cyrmaster
master Cyrus process
- Provided by: cyrus-common-2.4 (Version: 2.4.17+caldav~beta9-3)
- Source: cyrus-imapd-2.4
- Report a bug
master Cyrus process
cyrmaster [ -C alternate imapd.conf ] [ -M alternate cyrus.conf ] [ -l listen queue ] [ -p pidfile ] [ -P snmp agentx ping interval ] [ -j janitor period ] [ -d ] [ -D ] [ -x snmp agentx socket ]
cyrmaster is the process that controls all of the Cyrus processes. This process is responsible for creating all imapd, pop3d, lmtpd and sieved child processes. This process also initializes the Berkeley DB code and performs scheduled cleanup/maintenance.
If this process dies, then no new sessions will be started.
It kills itself and all child processes when it receives a SIGTERM.
Upon execution, cyrmaster reads its configuration information out of the cyrus.conf(5) file.
cyrmaster rereads its configuration file when it receives a hangup signal, SIGHUP. Services and events may be added, deleted or modified when the configuration file is reread. Any active services removed from the configuration file will be allowed to run until completion.
The environment variable CYRUS_VERBOSE can be set to log additional debugging information. Setting the value to 1 results in base level logging. Setting it higher results in more log messages being generated.
Services do not always go away silently when removed through a SIGHUP. If there are workers of the removed service still running, messages to syslog about broken pipes and accept() failures are to be expected.
The in-memory list of services is not cleaned up ever, so a cyrmaster daemon that has been sent an extremely high amount of SIGHUP signals to add/remove/modify services will lose performance eventually. Restarting cyrmaster fixes this.
cyrus.conf(5), imapd.conf(5), imapd(8), pop3d(8), lmtpd(8), timsieved(8), idled(8)