Simple / Usable things first
If you want a start script without much effort, you could use the upstart service. See the corresponding manual page and
/etc/init/*.conf for examples. After creating such a process you can start your server by calling
service my server start
If you want more features, like specific limitations or permission management, you could try
Using the shell
You could start your process like this:
nohup ./myexecutable &
& tells the shell to start the command in the background, keeping it in the job list. On some shells, the job is killed if the parent shell exits using the
HANGUP signal. To prevent this, you can launch your command using the nohup command, which discards the HANGUP signal.
However, this does not work, if the called process reconnects the HANGUP signal.
To be really sure, you need to remove the process from the shell's joblist. For two well known shells this can be achieved as follows:
bash: ./myexecutable & disown <pid> zsh: ./myexecutable &!
Killing your background job
Normally, the shell prints the PID of the process, which then can be killed using the kill command, to stop the server. If your shell does not print the PID, you can get it using
directly after execution. This prints the PID of the forked process.
Curated from this answer in SO.
Subscribe to Today I learned
Get the latest posts delivered right to your inbox