Getting started with GNU screen - Beginners Guide
Screen is a terminal multiplexer and has a wide feature set. It allows you to split your terminal window into multiple windows (split screen feature), detach sessions to let commands run in the background, connect to a device via serial interface, and many more. Screen sessions keep running even if you disconnect, which is especially great for unreliable connections. There are more advanced use cases, but we will focus on the basics.
You can have multiple sessions within the screen and each session can contain multiple windows. When you use the split screen function, each panel would be a window called region in screen.
screen │ │ ├───── session 29324.x │ │ │ ├────── window 0: name x │ │ │ └────── window 1: name y │ └───── session 29399.a │ ├───── window 0: name a │ └───── window 1: name b
Escape combination (Prefix) #
In this blog post, I'll call the escape combination 'prefix', but there are multiple names for it: meta key, leading key, escape combination, and some others.
The prefix tells the terminal that the following command or shortcut will be used in the screen context. Almost every shortcut starts with it and the default prefix is
a. So, if you see
Prefix in the reference section, I mean this key combination. I'll show you how to change the prefix as an example in the configuration section.
A list of all default key bindings can be found in the official documentaion.
Configuration files #
Screen won't create the startup configuration file by default but will look for these two files if it gets started.
Comments in the configuration file start with a
The following two sections will show some simple examples of different configurations.
Example 1: change prefix for screen
- Adding the following line to you your configuration file changes the prefix to
You can change it to a difference key combination, especially as the default prefix key combination is commonly used otherwise.
Example 2: turn off the copyright message at the start
#Do not show copyright msg at the start of a session startup_message off
Simply add these lines to your configuration file, and the copyright message won't appear again.
Before we start with the sessions and windows, it might be beneficial to talk about logging. For most troubleshooting sessions, it is required to save the logs. I am going to show you some ways to do it.
h to create an output file with the content of the current screen window you are in. It will be saved as
hardcopy.n ('n' for the number of the current window ) in the directory from where you have started the screen initially. If you repeat the shortcut, the initial file will be overwritten.
If you want to append the output to a file, you can add
hardcopy_append on to your configuration file.
If you want to change the directory in which the harcopy files will be saved, simply add
hardcopydir /your/dir/ to your configuration file.
Logging is disabled by default.
You can start a logged screen session with
-L flag +
-Logfile /path/to/logfile.txt. If you are already in a session, you can activate it with
h. The output file will be called
screenlog.n, where 'n' is the number of the current window.
Working with sessions #
- Show all sessions:
kuser@pleasejustwork:~$ screen -ls There are screens on: 29265.demo-session (27.01.2023 02:19:51) (Detached) 26508.pts-8.pleasejustwork (26.01.2023 23:20:50) (Detached) 2 Sockets in /run/screen/S-kuser.
- Start a new session:
- Start a new session with a specific name:
screen -S nameofthissession
- Start a new detached session and run a command:
screen -d -m ping 10.10.10.10
- Detach the current session:
- Re-attach session in terminal:
screen -r 2232# screen will auto complete if the prompt is unique
screen -r nameofthissession# either use the session number or the name
- Kill session in terminal:
screen -X -S nameofsession quit
screen -X 269 quit# auto-completes if unique
- Rename session in terminal:
screen -S OLDSESSIONNAME -X sessionname NEWSESSIONNAME
:sessionname NEW-NAME# screen command to change the current session name
Working with Windows #
- Show list of all windows of current session:
- Rename the current windows:
- Jump to the next window:
- Jump to the previous window:
- Kill the current window:
Working with Regions / Split screen #
Screen has the feature to show multiple windows in a split screen. Every window would then be a so called 'Region' in screen.
- Horizontally split window into two regions:
- Vertically split window into two regions:
- Jump to the next region:
- Close the current region:
- the window won't be terminated and just the split screen will be removed.
- Close all but the current region:
- Fit the regions to a resized terminal window:
You could create layouts, and save and reuse them later. This topic is out of the scope of this post and I am going to write about it later. You can get a reference and further information in the official documentaion.
Screen commands #
It can be used to try out configurations and screen-specific commands.
: + config
I am not too familiar with screen commands, so I won't go into detail. A list of all commands can be found in the official documentaion.
Check if you are still in a screen session #
Screen sets an environment variable
STY. If the output is empty, you are not in a screen session.
kuser@pleasejustwork:~$ echo $STY 22829.demo
This won't work if you start up screen and SSH into a remote machine. Without further configuration, the variables stay local.
Another environment variable you could try is
kuser@pleasejustwork:~$ screen kuser@pleasejustwork:~$ echo $TERM screen.xterm-256color kuser@pleasejustwork:~$ exit kuser@pleasejustwork:~$ echo $TERM xterm-256color
Screen will add the prefix
screen. in front of it.
This works even after connecting to a remote machine but presumes that you didn't mess with the
Another method would be to work with the screen prefix. You could simply use
t to let screen tell you the time in the bottom left corner.
E-Mail hello @itta vern. com
- 09.12.2022 Linux - connect to a serial port with screen
- 13.03.2023 My Offsite Backup - March 2023
- 10.03.2023 Getting started with iperf3 - Network Troubleshooting
- 05.03.2023 ICMP echo requests on Linux and Windows - Reference Guide
- 14.02.2023 Simulate an unreliable network connection with tc and netem on Linux
- 08.02.2023 Detecting Rogue DHCP Server