OS4X check running daemons

Which processes must run

In order to keep OS4X running, the following processes must exist:

• os4xrd: The OS4X master receive daemon (parent process of the subsequent receive daemon processes)
  • os4xrd_tcpip: The OS4X receive daemon for accepting TCP/IP connections
  • os4xrd_tcpip_tls: The OS4X receive daemon for accepting TLS secured TCP/IP connections for OFTP2
  • os4xrd_capi_0: The OS4X receive daemon for accepting ISDN connections on the first ISDN controller
  • (os4xrd_capi_x: subsequent ISDN controller receivig processes, if more controllers are configured)
• os4xsqd: OS4X send queue daemon. Parent process of running actions started by this process, like sending send queue entries, polling partners, updating CRLs etc.
• os4xdebugd: OS4X debug daemon which collects debugging information from every OS4X process for problem reporting

In case you have OS4X Enterprise, the following process must also exist:

• os4xclientd: OS4X client daemon, responsible for user authentification and OS4X Enterprise job processing

How do the processes save their state

Every OS4X daemon process saves its PID (process ID) in the database. If a value exists in the database on startup, the daemon refuses to start with the message that another daemon must be running at the moment. In some rare cases, the database information may not meet the real situation, when PIDs are saved in the database and no processes are running. In this case, you can start the daemon in 'forced' mode which overrides the PID check at daemon start.

Beware: If more than one daemon is running, racing conditions occur between the different running programs, mostly leading to problems in receiving or sending files. This situation is highly unsupported and absolutely to be avoided!