It's not uncommon for people to need to run commands in the Linux shell, whether on a local box or on a remote machine that you've SSHed into. Often we need these running programs to persist while we go and do other things. You can, of course, detach the process by putting an ampersand (&) after the command, but then we often can't see the outputs or interact if needed.
If we're on a local machine we can probably start a new shell and do stuff in there, but if we've used SSH then things aren't necessarily as clear-cut. Ideally we don't want to keep our SSH connection open for the entirety of the time the program is running just to keep it going, instead we want to be able to log in, start things running, log out, go and do other stuff, then log back in later and see the outputs from our program, or other information which is important.
This is where screen comes in. At it's most basic, which is all we're going to cover here, this is what screen allows you to do. We can do similar things on the local machine, and it's recommended that you try these out locally before attempting them over SSH. Assuming that we're working on a remote machine do the following:
Log in via SSH
Start the screen program by typing screen at the prompt.
some-console>$ screenIf screen is already installed you'll get a license blurb to read through, before it drops you into what appears to be a new shell session (if it's not then see below). Now run some commands as normal. Possibly start an ongoing process such as top.
Now we are going to detach our shell from the screen session. Do this by typing CTRL-"a" (Hold the control key down and press the "a" key at the same time - this is how we trigger screen commands) then press the "d" key (d for detach). You should see your shell revert to the previous prompt, possibly with a message that says something like:
[detached from 10525.pts-3.amos-ThinkPad-T430](That's a message on my laptop when I detach from a session)
The session, possibly containing a running instance of top is still there, we just can't see it at this point. To reattach our shell to a running screen session, we type screen -r at the prompt (this can even be inside a completely different shell window if we're working on the local machine). If you're using SSH then you can log out, then log back in and it will still work.
some-console>$ screen -rAs if by magic our previous screen session will reappear (you'll see top once more if that's what you left running).
Once you're happy doing this on your local machine, then try doing it over SSH on a machine you have control over. This is potentially one of the most useful commands you'll learn to use in conjunction with SSH as it allows you to persist your programs between logins.
[NOTE: If screen is not installed then you'll need to install it first using your package manager of choice (yum, pacman, apt-get, slapt-get or whatever your distribution prefers). This is probably as easy as doing sudo apt install screen on a Debian based distro. If not then you'll have to investigate how to do that, but that's beyond the scope of this article.]
To find out more about what the screen command can do then try typing man screen in the shell to bring up the man page which has all of the options and details about it. I've barely scratched the surface here.
Man Page for the screen command
There are other similar programs out there, such as tmux which I haven't used, but I may go and investigate now, and write a similar tutorial about.
My name is Dave Ames. I've been a teacher for 25 years and for the last few of those I've been teaching both children and other adults, especially teachers to program in a variety of environments, but mostly Python.
This is one of an occasional series of posts that I'm going to make about useful tools that live on the fringes of programming and using Linux in general.