In this lesson, you will learn how Linux organizes individual processes into "teams" so you can manage them as a single unit.
Understanding Process Groups
Think of a Process Group as a small project team. When you run a command in your shell—like grep "error" logfile | sort—the shell creates two separate processes. Because these processes are working together to complete one task, the shell puts them into the same Process Group.
Every process group has a leader: the Process Group ID (PGID) is usually the same as the PID of the first process started in that pipeline. This is vital for signaling. When you press Ctrl+C in your terminal, the shell doesn't send a signal to just one process; it sends the SIGINT interrupt signal to every process in the current foreground group. This ensures that the entire pipeline stops instantly, rather than leaving "zombie" pieces of the command running in the background.
Sessions: The Bigger Picture
A Session is a collection of one or more process groups. Think of a session as the entire "work environment" associated with your terminal login.
- The Session Leader: Usually the shell process itself.
- The Controlling Terminal: The session is tied to the TTY you are using.
When you log out, the kernel sends a SIGHUP (Hangup) signal to the session leader. The session leader then propagates this signal to every process group in its session. This is why closing your terminal window kills all the programs you started inside it—Linux is effectively "cleaning up" the entire session's project teams.
Why It Matters
This hierarchy allows the kernel to maintain order. Without these groups, your shell would have to manually track every single background process and individually kill them when you closed your terminal. By grouping them by Session and PGID, the operating system manages your entire computing environment through a simple, collective signal.
You can see these groupings yourself by running ps -eo pid,pgid,sid,cmd in your terminal. You will notice that many processes share the same PGID and SID because they belong to the same team and the same session.
Key Takeaway: Process groups allow the system to send a single command to an entire team of processes, while sessions ensure that your entire workspace is cleaned up when you disconnect your terminal.