Normally, when you log into a remote server via SSH, you get one command prompt and so there’s essentially only one thing you can do at a time without a lot of extra hassle. However, most of the time I (and presumably others like me) need to do lots of things, potentially in different directories spread out all over the place. Since switching back and forth between directories all the time is only one of those hassles I mentioned, more often than not I end up with multiple SSH connections to the same server.
Like a couple days ago–I had a connection open to edit my files, one to handle my version control (Mercurial, if you’re curious–more on that later), and one to keep tabs on my data. Juggling multiple connections like that is easy in a GUI–a couple of quick “Alt-Tabs” and you’ve gone from your editor to your data directory to your version control and back again. However, all those connections can eat up your bandwidth and many other less-than-fun things, especially when there’s a handy little tool around to do the same kind of thing built right in to the Linux (and presumably other Unix-like OS’s)–the screen command.
The screen command essentially allows you to create multiple “windows” or “screens” you can use within the same connection. You get multiple command prompts you can work with, and a handy keyboard shortcut similar to but slightly less convenient than “Alt-Tab” to switch between your “screens”. Another benefit to using screen is that your sessions can survive across SSH sessions–you can disconnect from your screen, log off the server, go away to do something more fun for a couple hours, log back in, and resume right where you left off–same environmental variables, same directory, same command history, etc. You can even use screen to run long-running commands (say, a command that takes hours or days to run) without having to stay logged in the whole time. Pretty cool, huh?
You can get most of the information you need to use the screen command effectively out of the man page (this one’s not bad), but I’ll summarize the pieces I find most useful here.
First off, you need to create a new screen, ideally with a name, so you can resume them more easily later and not have to remember a weird id number. To make a screen named “screenTest” for example, run the following command:
screen -S screenTest
You should be switched over to a new command prompt and see something like “[screen 0: bash]” in your SSH session’s title, assuming your SSH client supports that kind of change.
The next thing you need to know is how to create what I call a “subscreen,” though I don’t think that’s an official term. (I’d run a simple command like “ls” now so you can tell the difference between your “subscreens.”) Hit CTRL+A, release them both, and hit C. Once again, you should see a new command prompt and something like “[screen 1: bash]” in your window’s title. Switch back and forth between your “subscreens” by hitting CTRL+A twice just to see that you can, or until you’re convinced there’s a difference between the two. If you have more than two subscreens, you need to know about a couple more things about subscreen navigation:
- CTRL+A twice navigates to the most recently used subscreen.
- CTRL+A, N navigates to the “next” subscreen in your list of subscreens.
- CTRL+A, P navigates to the “previous” subscreen in your list.
- CTRL+A, 0 navigates to the screen numbered 0. You can use any number between 0-9 for the same effect.
- CTRL+A, ” opens up a list of the screens you can move between.
- CTRL+A, ‘ prompts you for a screen number and allows you to bounce straight to that screen.
Now, it’s time to drop out of your screens as if you were going to log out. Hit CTRL+A followed by D, and you should be “detached” from your current screen. You’ll have returned to your original command prompt, with a little “[detached]” message right after your screen command.
Let’s pretend you wandered away from your computer and came back, ready to start work again. You need to resume your previous session, so run this command.
screen -r screenTest
Voilà! Your screen should open up, just like it was when you detached from it earlier (unless you were running a long command, in which case the output is probably different, but that’s beside the point). Having fun yet?
One more thing that you might need to know is how to connect to a screen that’s already attached somewhere else, or that didn’t get detached properly somehow (I’ve had it happen once or twice). This one’s pretty obvious, as well.
screen -d screenTest
If you pass the “-r” flag to that command, as well, you will detach the other session and connect to it yourself, which can be helpful if you’re moving between computers or something like that.
When it’s time to nuke a screen completely (like if you were a smart person and set up separate screens for each project you’re working on, and just finished one of them), getting rid of it is really easy. Attach to it, and hit CTRL+D until you close out all of the subscreens. Be careful you don’t nuke your real session, though, because it’s really easy to do.
One caveat–if you use screen a lot, get used to piping things through less, since the scroll bar of your window will do strange things while you’re running screen.
Ok, that takes care of the basics. Have fun!