mirror of
https://github.com/processone/ejabberd.git
synced 2024-06-02 21:17:12 +02:00
5c6ffaafd6
Daemons started by systemd shouldn't fork into the background if possible, because if multiple forked processes exist, systemd has a hard time determining the main process ID. In a memory constrained environment, the OOM killer may cause ejabberd to exit without any trace. Because epmd keeps running, systemd wouldn't notice the error condition, and as a result it won't restart the server. With ejabberd running in foreground, systemd is able to obtain the correct exit code (137 in this case, instead of 0) and schedules a restart. The administrator can then see what happend by looking at systemctl status ejabberd.
19 lines
411 B
Plaintext
19 lines
411 B
Plaintext
[Unit]
|
|
Description=XMPP Server
|
|
After=network.target
|
|
|
|
[Service]
|
|
User=ejabberd
|
|
Group=ejabberd
|
|
LimitNOFILE=65536
|
|
Restart=on-failure
|
|
RestartSec=5
|
|
ExecStart=@ctlscriptpath@/ejabberdctl foreground
|
|
ExecStop=/bin/sh -c '@ctlscriptpath@/ejabberdctl stop && @ctlscriptpath@/ejabberdctl stopped'
|
|
ExecReload=@ctlscriptpath@/ejabberdctl reload_config
|
|
PrivateDevices=true
|
|
TimeoutSec=300
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|