StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<h1>Simple / Usable things first</h1> <p>If you want a start script without much effort, you could use the <code>upstart</code> service. See the corresponding manual page and <code>/etc/init/*.conf</code> for examples. After creating such a process you can start your server by calling</p> <pre><code>service myserver start </code></pre> <p>If you want more features, like specific limitations or permission management, you could try <code>xinetd</code>.</p> <h1>Using the shell</h1> <p>You could start your process like this:</p> <pre><code>nohup ./myexecutable & </code></pre> <p>The <code>&</code> 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 <code>nohup</code> command, which discards the HANGUP signal.</p> <p>However, this does not work, if the called process reconnects the HANGUP signal.</p> <p>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:</p> <h3>bash:</h3> <pre><code>./myexecutable & disown <pid> </code></pre> <h3>zsh:</h3> <pre><code>./myexecutable &! </code></pre> <h2>Killing your background job</h2> <p>Normally, the shell prints the PID of the process, which then can be killed using the <code>kill</code> command, to stop the server. If your shell does not print the PID, you can get it using</p> <pre><code>echo $! </code></pre> <p>directly after execution. This prints the PID of the forked process.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload