Difference between revisions of "OS4X Core start daemons"
Jump to navigation
Jump to search
(New page: == List of daemons == In order to start OS4X, you first have to understand which program is responsible for which task. So, here a list for exactly this information: *os4xrd: receiving pro...) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
*os4xrd: receiving process which accepts incoming calls, transfers files and meta information | *os4xrd: receiving process which accepts incoming calls, transfers files and meta information | ||
*os4xsqd: send queue daemon, which is responsible to send files of the send queue to a defined partner | *os4xsqd: send queue daemon, which is responsible to send files of the send queue to a defined partner | ||
| − | |||
*os4xclientd: client daemon, responsible for job handling and authentification of OS4X Enterprise user sessions | *os4xclientd: client daemon, responsible for job handling and authentification of OS4X Enterprise user sessions | ||
| + | *os4xdebugd: debug daemon, which collects information about all running processes and writes them out on demand in an encrypted form. It should only be started in debug cases (i.e. when told so by the support team) since it allocates much system ressources. Also, race conditions are possible. | ||
| Line 10: | Line 10: | ||
*[[OS4X Core binaries#os4xrd_.2F_os4xrd2|os4xrd]] | *[[OS4X Core binaries#os4xrd_.2F_os4xrd2|os4xrd]] | ||
*[[OS4X Core binaries#os4xsqd_.2F_os4xsqd2|os4xsqd]] | *[[OS4X Core binaries#os4xsqd_.2F_os4xsqd2|os4xsqd]] | ||
| − | |||
| − | |||
In case of an OS4X Enterprise installation, you have to start these four daemons right after the configuration: | In case of an OS4X Enterprise installation, you have to start these four daemons right after the configuration: | ||
*[[OS4X Core binaries#os4xrd_.2F_os4xrd2|os4xrd]] | *[[OS4X Core binaries#os4xrd_.2F_os4xrd2|os4xrd]] | ||
*[[OS4X Core binaries#os4xsqd_.2F_os4xsqd2|os4xsqd]] | *[[OS4X Core binaries#os4xsqd_.2F_os4xsqd2|os4xsqd]] | ||
| − | |||
*os4xclientd | *os4xclientd | ||
| Line 28: | Line 25: | ||
root 4391 4388 0 22:43 ? 00:00:00 os4xrd_capi_0 | root 4391 4388 0 22:43 ? 00:00:00 os4xrd_capi_0 | ||
root 4394 1 0 22:43 ? 00:00:00 /opt/os4x/bin/os4xsqd | root 4394 1 0 22:43 ? 00:00:00 /opt/os4x/bin/os4xsqd | ||
| − | |||
Expect that "''os4xrd''" forks some processes for incoming medias, as documented [[OS4X Core binaries#os4xrd_.2F_os4xrd2|here]]. | Expect that "''os4xrd''" forks some processes for incoming medias, as documented [[OS4X Core binaries#os4xrd_.2F_os4xrd2|here]]. | ||
| + | |||
| + | |||
| + | In case of an OS4X Enterprise installation, the daemon "''os4xclientd''" should be visible too: | ||
| + | root 4399 1 0 22:43 ? 00:00:00 /opt/os4x/bin/os4xclientd | ||
Latest revision as of 14:21, 10 October 2024
List of daemons
In order to start OS4X, you first have to understand which program is responsible for which task. So, here a list for exactly this information:
- os4xrd: receiving process which accepts incoming calls, transfers files and meta information
- os4xsqd: send queue daemon, which is responsible to send files of the send queue to a defined partner
- os4xclientd: client daemon, responsible for job handling and authentification of OS4X Enterprise user sessions
- os4xdebugd: debug daemon, which collects information about all running processes and writes them out on demand in an encrypted form. It should only be started in debug cases (i.e. when told so by the support team) since it allocates much system ressources. Also, race conditions are possible.
So, if you are running an OS4X Core installation without OS4X Enterprise, you will have to start the three daemons
In case of an OS4X Enterprise installation, you have to start these four daemons right after the configuration:
If you want to check if everything works fine, you should check your process list:
ps -ef | grep os4x | grep -v grep
In case of a OS4X Core installation with one ISDN controller defined, you should get something like this:
root 4388 1 0 22:43 ? 00:00:00 /opt/os4x/bin/os4xrd root 4389 4388 0 22:43 ? 00:00:00 os4xrd_tcpip root 4390 4388 0 22:43 ? 00:00:00 os4xrd_tcpip_tls root 4391 4388 0 22:43 ? 00:00:00 os4xrd_capi_0 root 4394 1 0 22:43 ? 00:00:00 /opt/os4x/bin/os4xsqd
Expect that "os4xrd" forks some processes for incoming medias, as documented here.
In case of an OS4X Enterprise installation, the daemon "os4xclientd" should be visible too:
root 4399 1 0 22:43 ? 00:00:00 /opt/os4x/bin/os4xclientd