Terminating Detached GNU Screen Sessions in Linux: Complete Guide and Best Practices

Fundamentals of GNU Screen Session Management

GNU Screen is a terminal multiplexer that allows users to create multiple virtual terminal sessions within a single terminal window. These sessions can continue running after users disconnect from SSH connections, making them particularly suitable for long-running background tasks. When sessions are no longer needed, properly terminating them is crucial to avoid resource waste and potential system issues.

Listing Existing Screen Sessions

Before terminating any Screen session, it's essential to identify currently running sessions. The screen -ls command lists all active Screen sessions, including both detached and attached sessions.

screen -ls

The command output displays session IDs, session names, and status information. For example:

There are screens on:
    20751.Melvin_Peter_V42  (Detached)
    20863.session_1         (Detached)

Session IDs typically consist of a process ID and session name, which are used in subsequent termination operations.

Core Methods for Terminating Screen Sessions

Based on analysis of Q&A data and reference articles, there are two main approaches to terminating Screen sessions: directly using the quit command to terminate entire sessions, or attaching to sessions and manually exiting.

Direct Session Termination Using quit Command

This is the most efficient method, particularly suitable for managing multiple sessions in bulk. The -X parameter of the screen command sends commands to running Screen sessions, the -S parameter specifies the target session, and the quit command terminates the entire session.

screen -X -S [session_id] quit

In practical applications, [session_id] should be replaced with the specific session identifier. For example, to terminate session 20751.Melvin_Peter_V42:

screen -X -S 20751.Melvin_Peter_V42 quit

This method doesn't require users to attach to sessions, completing termination operations directly through command line, making it ideal for automation scripts and remote management.

Differences Between kill and quit Commands

The Q&A data clearly indicates that using the kill command only terminates individual windows within Screen sessions, while the quit command terminates entire sessions. This is an important distinction that helps prevent operational errors.

Usage of kill command:

screen -X -S [session_id] kill

This command only closes the currently active window. If the session contains multiple windows, other windows will continue running. In contrast, the quit command completely terminates the entire session and all its windows.

Manual Termination After Session Attachment

Another approach involves first attaching to the target session, then performing exit operations within the session. Although this method involves more steps, it provides better control, particularly suitable for scenarios where session status needs verification before termination decisions.

First attach to the session:

screen -r [session_id]

After entering the session, use either of the following methods to terminate the session:

exit

Or use Screen's internal command:

Ctrl+A, :quit

If the session contains multiple windows, the exit command must be executed in each window until all windows are closed before the session completely terminates.

Handling Dead Sessions and Cleanup Operations

Sometimes Screen sessions may enter dead states due to abnormal termination. These sessions appear as dead sessions in the screen -ls listing. The screen -wipe command cleans up these invalid session records.

screen -wipe

This command scans all Screen sessions, removing entries for sessions that have terminated but whose session records still exist, maintaining a clean session list.

Best Practices for Screen Session Management

Based on experience sharing from reference articles, here are some best practices for Screen session management:

Create named sessions for easier management:

screen -S training_session

Create daemon sessions with output logging:

screen -dmLS data_processing python process_data.py

Properly detach from sessions (using Ctrl+A, D instead of directly exiting terminal):

Ctrl+A, D

Regularly check session status:

screen -ls

Alternative Solution: nohup Command

Besides Screen, the nohup command is another common tool for managing long-running processes. nohup ensures commands continue running after users log out and redirects output to the nohup.out file.

nohup python train_model.py &

Compared to Screen, nohup is more lightweight but lacks Screen's multi-window management and session recovery capabilities.

Conclusion and Recommendations

When terminating detached Screen sessions, using the screen -X -S [session_id] quit command is recommended as the most direct and effective method. Avoid using the kill command since it only terminates individual windows rather than entire sessions. For abnormally terminated sessions, use screen -wipe for cleanup. In daily usage, it's advisable to name important sessions, regularly check session status, and promptly terminate sessions when no longer needed to release system resources.