In this lesson, you will learn how the shell, acting as a "session leader," manages the lifecycle of your programs when a terminal connection is lost.
What is a Session Leader?
When you log into a terminal, the shell is usually assigned as the session leader. This role makes the shell the primary supervisor for all the processes that follow. Think of the session leader as the captain of a ship; its primary duty is to keep track of its crew—your running programs—and decide what happens if the "ship" (your terminal connection) sinks.
The Cleanup Trigger
When you close your terminal window or lose your internet connection during an SSH session, the operating system detects that the communication channel is broken. It notifies the session leader by sending a SIGHUP (Signal Hang-up) signal.
The session leader has a critical responsibility here: it must broadcast this signal to all the processes it launched. By default, this causes your active pipelines and background tasks to terminate. This is a safety mechanism to prevent "orphaned" processes from running indefinitely without an owner to control them or view their output.
Observing the Behavior
If you run a background job in a terminal and then close that terminal, you can see this in action. The shell ensures the environment is cleaned up. You can test this by running a process and checking the /proc filesystem:
# Start a process in the background
sleep 1000 &
# Find its process ID (PID)
echo $!
# Close your terminal window and reconnect
# Check if the process is still running
ls /proc/[PID]
When you return, you will likely find that the directory for that PID no longer exists. The session leader fulfilled its duty by propagating the hang-up signal and cleaning up the process group.
This mechanism ensures that your system doesn't become cluttered with "zombie" or runaway processes every time a connection drops. If you want a process to ignore these responsibilities and keep running after the session leader departs, you would typically need to use tools that decouple the process from the terminal’s signal chain—but the default, orderly behavior is to clear the deck when the captain leaves.
Key Takeaway: A session leader is responsible for propagating hang-up signals to its process group, ensuring that child processes are cleaned up when the terminal connection terminates.