Problem with PuTTY

Hey

I just switched from a virtual Windows to a dedicated linux Server to get more perfomance ( 64GB RAM , i7 6700, 1Gb Up/Download ). Im hosting a Teamspeak3 and a GarrysMod ( Gaming ) Server on that server. I already used Linux and thought that it would be great because of the saved CPU Power and the securtiy. Acctually the Teamspeak and the Gaming Server are working perfectly, but if im closing PuTTY, the Gaming-Server automaticly shut down but the Teamspeak-Server keeps online. So I have to lauch PeTTY all day long on my PC to keep the Gamingserver alife. Do you guys eventually know how to fix that problem?

Greets,
Chris

End the command line with & I guess?

A little more information would help us help you:
What version/distro of Linux are you running?
How are you starting the Teamspeak3 server?
How are you starting the Gaming server?

Originally Posted by shruggy End the command line with & I guess?

That'll run the specific command in the background.

The proper solution is to setup a service, which can be configured to start on boot and auto-restart on crashes.

Most server software comes with the relevant service scripts and setup instructions - if whatever version of Garry's Mod server the OP is using doesn't do that, using LinuxGSM's version as per the following pages would appear to be a solution...
https://linuxgsm.com/lgsm/gmodserver/
https://docs.linuxgsm.com/configuration/running-on-boot

Hey scasey,

The server runs on Ubuntu 16.04. Im starting teamspeak via the files and then "./ts3server_startscript.sh start". If I want to start the GMod-Server im going into the files and then start the server with "./srcds_run".

Originally Posted by LordHomeboy Hey scasey, The server runs on Ubuntu 16.04. Im starting teamspeak via the files and then "./ts3server_startscript.sh start". If I want to start the GMod-Server im going into the files and then start the server with "./srcds_run".

If you do that in a putty session, most processes started during the session will end with the session. That is what you are observing, Options are to start it outside of any session (ie: as a service}, or in a way that will ignore the session hangup (nohup and background). Changing the astart from "command" to "nohup command &" starts it in the background ignoring hangup.

The technical reason is the gmod server is attached to the putty terminal session and when you quit putty the server will quit too.

The method to automatically start the server as suggested by the gmod wiki is a cron job.
https://wiki.facepunch.com/gmod/Linu...Server_Hosting

If you don't want to start automatically you can use tmux or screen to disconnect the server from putty.

Teamspeak is configured as a service so it does not need to be disconnected from putty and how to automatically start it is provided by the links above.

Another option to fix this would be once you login with putty, then start a screen session and then start the applictions in that. Disconnect from the screen session and you can close putty.
Latter you can connect with putty and reattach to the screen session with "screen -r"

Originally Posted by wpeckham If you do that in a putty session, most processes started during the session will end with the session. That is what you are observing, Options are to start it outside of any session (ie: as a service}, or in a way that will ignore the session hangup (nohup and background). Changing the astart from "command" to "nohup command &" starts it in the background ignoring hangup.

Its seems like it works! But how can I stop the server?

to kill the server use the 'kill' command and the proecss name.

 kill -15 name

-15 will try to kill it gracefully, other use -9 to force kill it.

Originally Posted by uteck to kill the server use the 'kill' command and the proecss name.

The default kill command will need a process ID:

kill [-s signal|-p] [-q sigval] [-a] [--] pid...

in which pid... is a list of process id's.
Some shells have an extended, built-in version of kill, i.e. bash:

kill [-s sigspec | -n signum | -sigspec] [pid | jobspec] ...

(from man bash), but that is an extension:

the processes named by pid or jobspec.

(from the same man page).

I meant to type pkill, which will take a program or presess name without having to track down the pid.

Originally Posted by uteck Another option to fix this would be once you login with putty, then start a screen session and then start the applictions in that. Disconnect from the screen session and you can close putty. Latter you can connect with putty and reattach to the screen session with "screen -r"

I also recommend this, I used screen extensively when I hosted different game-servers since I wanted easy access to the console live feed etc.

https://linuxize.com/post/how-to-use-linux-screen/

Originally Posted by Plankt0n I also recommend this, I used screen extensively when I hosted different game-servers since I wanted easy access to the console live feed etc. https://linuxize.com/post/how-to-use-linux-screen/

I also use screen (and screenie, one of many screen front ends that make it "friendlier") and recommend it highly. I do not generally recommend it for starting services. While it would work, one of the other options would be lighter and more efficient. Your call, of course.

To be clear, even if you do not use screen for this specific purpose, it is something you will value once you learn to use it.