OS4X Core start daemons

From OS4X
Revision as of 20:44, 23 September 2007 by Admin (talk | contribs) (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...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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
  • os4xdebugd: debug daemon, which collects information about all running processes and writes them out on demand in an encrypted form
  • os4xclientd: client daemon, responsible for job handling and authentification of OS4X Enterprise user sessions


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
root      4397     1  0 22:43 ?        00:00:00 /opt/os4x/bin/os4xdebugd

Expect that "os4xrd" forks some processes for incoming medias, as documented here.