Include systemd documentation for run on boot#3
Include systemd documentation for run on boot#3dgibbs64 merged 3 commits intoGameServerManagers:masterfrom Chrzi:patch-1
Conversation
systemd is the default init system for most modern distros and should be preferred over crontabs and SysVinit I included a simple service file for a teamspeak 3 server that can be easily adopted to other servers as well/
Forking type did not work as systemd could not reliably determine the PID of the actual server.
|
You could use systemd timers (that work just like cronjobs), but with the unit files itself currently no. Systemd could detect with the process died and try to restart it then, but this fails because the LGSM script is forking to tmux and exits after that, without a PID file systemd can not reliably determine the main process of the actual server. https://www.freedesktop.org/software/systemd/man/systemd.service.html |
|
Thanks for this. system.d is a little more complicated to install than just using cronjobs and achieves the same result. Having said that it is a very good idea to include this method as it is the current standard. I might be a good idea for LinuxGSM to automate the installation of a system.d service maybe using adding a new command allowing admins to use use the command |
Merge pull request #11 from AntonnMal/master
systemd is the default init system for most modern distros and should be preferred over crontabs and SysVinit
I included a simple service file for a teamspeak 3 server that can be easily adopted to other servers as well