Running on Boot
systemd is the default init system for most modern distros.
You need to create a service file in
/etc/systemd/system/Example
ts3server.service[Unit]
Description=LinuxGSM Teamspeak3 Server
After=network-online.target
Wants=network-online.target
[Service]
Type=forking
User=ts3server
WorkingDirectory=/home/ts3server
#Assume that the service is running after main process exits with code 0
RemainAfterExit=yes
ExecStart=/home/ts3server/ts3server start
ExecStop=/home/ts3server/ts3server stop
Restart=no
[Install]
WantedBy=multi-user.target
Replace the user and paths to fit your setup.
You need to reload the systemd-daemon once to make it aware of the new service file by
systemctl daemon-reloadNow you can do
systemctl start ts3server # Start the server
systemctl stop ts3server # Stop the server
systemctl enable ts3server # Enable start on boot
systemctl disable ts3server # Disable start on boot
The crontab will allow you to create cronjobs that allow you to run a command on a set time or on boot. The below example uses
@reboot that will run a command on boot. @reboot '/home/username/gameserver monitor' > /dev/null 2>&1
Most admins will also have a timed monitor cronjob configured. If you do not want to have extra cronjobs the timed monitor will also start a server but with a timed delay.
After a reboot, any game server that has a "started" status will be started on boot. Servers that were manually stopped will remain stopped.
crontab -e
@reboot su - username -c '/home/username/gameserver monitor' > /dev/null 2>&1
Start a game server unconditionally, even if you manually stop a server.
crontab -e
@reboot su - username -c '/home/username/gameserver start' > /dev/null 2>&1
rc.local is another method to run scripts on boot. Any commands added to the rc.local file will run on boot.
nano /etc/rc.local
su - username -c '/home/username/gameserver start'
Last modified 1mo ago