Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Assuming you are on a Unix/Linux system, you can run it in a <code>screen</code> session. (This is a Unix command, not a scripting function.)</p> <p>If you don't know what <code>screen</code> is, it's basically a "detachable" terminal session. You can open a <code>screen</code> session, run this script, and then detach from that <code>screen</code> session. That detached session will stay alive even after you log off, leaving your script running. (You can re-attach to that <code>screen</code> session later if you want to shut it down manually.)</p> <p><code>screen</code> is pretty neat, and every developer on Unix/Linux should be aware of it.</p> <p><strong>How to do this without reading any docs:</strong></p> <ul> <li>open a terminal session on the server that will run the script</li> <li>run <code>screen</code> - you will now be in a new shell prompt in a new screen session</li> <li>run your script</li> <li>type <code>ctrl-a</code> then <code>d</code> (without ctrl; the "d" is for "detach") to detach from the <code>screen</code> (but still leave it running)</li> </ul> <p>Now you're back in your first shell. Your script is still alive in your <code>screen</code> session. You can disconnect and the <code>screen</code> session will keep on trucking.</p> <p>Do you want to get back into that <code>screen</code> and shut the app down manually? Easy! Run <code>screen -r</code> (for "reattach"). To kill the <code>screen</code> session, just reattach and exit the shell.</p> <p>You can have multiple <code>screen</code> sessions running concurrently, too. (If there is more than one <code>screen</code> running, you'll need to provide an argument to <code>screen -r</code>.)</p> <p><strong>Check out some <code>screen</code> docs!</strong></p> <p><a href="http://www.phacks.net/how-to-use-gnu-screen/" rel="nofollow">Here's a screen howto.</a> Search "gnu screen howto" for many more.</p>
 

Querying!

 
Guidance

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