Chapril/xmpp.chapril.org-ejabberd
25
1
Fork 0
mirror of https://github.com/processone/ejabberd.git synced 2024-11-20 16:15:59 +01:00
Code Releases Activity
07e20784cb
xmpp.chapril.org-ejabberd/ejabberd.service.template

22 lines
491 B
Plaintext
Raw Normal View History

Add script for systemd (Guthub #434)
2015-02-23 15:52:18 +01:00
[Unit]
Description=XMPP Server
After=network.target
[Service]
Integrate nicely with systemd Support systemd's watchdog feature and enable it by default in the unit file, so that ejabberd is auto-restarted if the VM becomes unresponsive. Also, set the systemd startup type to 'notify', so that startup of followup units is delayed until ejabberd signals readiness. While at it, also notify systemd of configuration reload and shutdown states. Note: "NotifyAccess=all" is required as long as "ejabberdctl foreground" runs the VM as a new child process, rather than "exec"ing it. This way, systemd views the ejabberdctl process itself as the main service process, and would discard notifications from other processes by default.
2021-01-06 00:20:12 +01:00
Type=notify
Use the configured user in systemd's ejabberd.service
2021-10-06 12:18:08 +02:00
User=@installuser@
Group=@installuser@
Increase file descriptor limit in systemd unit 16,000 file descriptors will only suffice for small setups.
2016-10-20 00:12:02 +02:00
LimitNOFILE=65536
Let systemd restart ejabberd on failure The "RestartSec=5" setting has no effect if "Restart" is not also specified.
2016-10-19 23:35:22 +02:00
Restart=on-failure
Add script for systemd (Guthub #434)
2015-02-23 15:52:18 +01:00
RestartSec=5
Let systemd start ejabberd in foreground 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.
2020-11-19 20:43:51 +01:00
ExecStart=@ctlscriptpath@/ejabberdctl foreground
Let systemd stop ejabberd gracefully Make sure the "ExecStop" command line blocks until ejabberd is actually stopped. This prevents systemd from killing the ejabberd process(es) immediately. Also, let the "ExecStart" command line block until ejabberd's startup is completed. This makes sure that services which depend on ejabberd aren't started up too early.
2016-10-20 00:27:50 +02:00
ExecStop=/bin/sh -c '@ctlscriptpath@/ejabberdctl stop && @ctlscriptpath@/ejabberdctl stopped'
Specify "ExecReload" command in systemd unit Now that "ejabberdctl reload_config" works the way most admins would expect, expose the command via systemd.
2017-02-23 18:16:56 +01:00
ExecReload=@ctlscriptpath@/ejabberdctl reload_config
Integrate nicely with systemd Support systemd's watchdog feature and enable it by default in the unit file, so that ejabberd is auto-restarted if the VM becomes unresponsive. Also, set the systemd startup type to 'notify', so that startup of followup units is delayed until ejabberd signals readiness. While at it, also notify systemd of configuration reload and shutdown states. Note: "NotifyAccess=all" is required as long as "ejabberdctl foreground" runs the VM as a new child process, rather than "exec"ing it. This way, systemd views the ejabberdctl process itself as the main service process, and would discard notifications from other processes by default.
2021-01-06 00:20:12 +01:00
NotifyAccess=all
Harden the systemd unit Restrict capabilities, have a private tmp directory, private /dev, and don't accessing file system locations that really shouldn't be accessed.
2016-06-28 23:02:41 +02:00
PrivateDevices=true
Allow for listening on privileged ports Let systemd give ejabberd the capability to bind to ports below 1024.
2021-01-06 18:56:08 +01:00
AmbientCapabilities=CAP_NET_BIND_SERVICE
Increase start-up/stop timeout in systemd unit On slow systems, it can take quite a while for "ejabberdctl started" and/or "ejabberdctl stopped" to return.
2018-06-07 17:40:05 +02:00
TimeoutSec=300
Add script for systemd (Guthub #434)
2015-02-23 15:52:18 +01:00
[Install]
WantedBy=multi-user.target
Copy Permalink