Search Our Database

Introduction

In Linux server environments, long-running processes such as system updates, file transfers, or script executions are common. Managing these tasks over SSH can become problematic if the session is interrupted or disconnected, leading to task termination. The screen utility is a terminal multiplexer designed to address this issue, allowing users to start a session, run processes, detach from the session, and later resume it — even from a different device or after disconnection.

The screen command is particularly useful for system administrators, developers, and remote users who work with terminal-based environments. It is applicable in scenarios where background execution, persistent sessions, or multi-task terminal management is required. For example, when running commands like compiling software, maintaining SSH sessions to remote servers, or monitoring logs and processes continuously, screen ensures that the task remains active even if the terminal closes.

Understanding screen is crucial in multi-user systems, development operations, and automated task environments. It simplifies parallel session management and minimizes the risks of task interruptions. Compared to alternatives like tmux, screen is older but widely supported and available by default on many Linux distributions.

This guide explains how to install, create, manage, and terminate screen sessions to reliably perform tasks. Common use cases include managing remote scripts, monitoring long-running background jobs, or installing software packages that require uninterrupted execution. It also covers potential pitfalls such as forgotten sessions, orphaned processes, and best practices to manage session logs and cleanup.

By the end of this guide, readers will be able to effectively use screen to run background tasks, monitor their output, and resume sessions at will, ensuring greater stability and control over terminal-based processes.

Prerequisites

• A Linux-based system (Debian, Ubuntu, CentOS, Rocky Linux, etc.)
• Access to a terminal or SSH session
• Superuser (root) privileges or a user account with sudo access
• screen version 4.06 or later recommended (run screen –version to check)

Step-by-step Guide

Step 1: Install screen

Most modern Linux distributions include screen by default. If it is not installed, use the package manager to install it.

For Debian/Ubuntu:

sudo apt update
sudo apt install screen

For CentOS/RHEL/Rocky Linux:

sudo yum install screen

To confirm the installation:

screen --version

Step 2: Start a New screen Session

Create a new screen session with a specific name for easier management.

screen -S mysession

This command opens a new terminal session named mysession. From this point, any command executed will run inside the screen environment.

Step 3: Run Tasks Within the screen session

With the screen session active, execute any long-running command or process.

Example:

sudo apt upgrade

Even if the SSH connection is lost, the command will continue running in the background.

Step 4: Detach from the screen Session

To safely exit the screen session and leave the process running:

Press:

Ctrl + A, then D

This key combination detaches the session and returns to the standard terminal.

Step 5: List Active screen Sessions

To view all detached and active screen sessions:

screen -ls

Example output:

There is a screen on:
    3284.mysession    (Detached)
1 Socket in /run/screen/S-root.

Step 6: Reattach to an Existing Session

To resume work within a detached session:

screen -r mysession

If only one session exists, running screen -r without a name will reattach automatically.

Step 7: Terminate a screen Session

To close a screen session properly, exit the running process or type exit in the screen shell:

exit

This will terminate the session and any running processes.

Conclusion

The screen utility provides a reliable method for managing long-running terminal sessions on Linux. By allowing users to detach, reattach, and persist tasks across sessions, it plays a vital role in server management and remote development. It is especially beneficial in environments where SSH disconnections are common, or when background processing is required without relying on additional tools.

Users are encouraged to familiarize themselves with advanced features such as split windows, logging, and multi-user access to enhance productivity.

Should you have any inquiries about the guidelines, please feel free to open a ticket through your portal account or contact us at support@ipserverone.com. We’ll be happy to assist you further.