Process group
In a POSIX-conformant operating system, a process group denotes a collection of one or more processes. Among other things, a process group is used to control the distribution of a signal; when a signal is directed to a process group, the signal is delivered to each process that is a member of the group. Similarly, a session denotes a collection of one or more process groups. A process may not create a process group that belongs to another session; furthermore, a process is not permitted to join a process group that is a member of another session—that is, a process is not permitted to migrate from one session to another. When a process replaces its image with a new image (by calling one of the exec functions), the new image is subjected to the same process group (and thus session) membership as the old image.
In a POSIX-conformant operating system, a process group denotes a collection of one or more processes.[1] Among other things, a process group is used to control the distribution of a signal; when a signal is directed to a process group, the signal is delivered to each process that is a member of the group.[2]
Similarly, a session denotes a collection of one or more process groups.[3] A process may not create a process group that belongs to another session; furthermore, a process is not permitted to join a process group that is a member of another session—that is, a process is not permitted to migrate from one session to another.
When a process replaces its image with a new image (by calling one of the exec functions), the new image is subjected to the same process group (and thus session) membership as the old image.
Applications
[edit]The distribution of signals to process groups forms the basis of job control employed by shell programs. The TTY device driver incorporates a notion of a foreground process group, to which it sends signals generated by keyboard interrupts, notably SIGINT ("interrupt", Control+C), SIGTSTP ("terminal stop", Control+Z), and SIGQUIT ("quit", Control+\). It also sends the SIGTTIN and SIGTTOU signals to any processes that attempt to read from or write to the terminal and that are not in the foreground process group. The shell, in turn, partitions the command pipelines that it creates into process groups, and controls what process group is the foreground process group of its controlling terminal, thus determining what processes (and thus what command pipelines) may perform I/O to and from the terminal at any given time.
When the shell forks a new child process for a command pipeline, both the parent shell process and the child process immediately make the child process the leader of the process group for the command pipeline. This ensures that the child is the leader of the process group before either the parent or child relies on this being the case.
Where a textual user interface is being used on a Unix-like system, sessions are used to implement login sessions. A single process, the session leader, interacts with the controlling terminal in order to ensure that all programs are terminated when a user "hangs up" the terminal connection. (Where a session leader is absent, the processes in the terminal's foreground process group are expected to handle hangups.)
Where a graphical user interface is being used, the session concept is largely lost, and the kernel's notion of sessions largely ignored. Graphical user interfaces, such as where the X display manager is employed, use a different mechanism for implementing login sessions.
Details
[edit]The system call setsid is used to create a new session containing a single (new) process group, with the current process as both the session leader and the process group leader of that single process group.[4]
Process groups are identified by a positive integer, the process group ID, which is the process identifier of the process that is (or was) the process group leader.
Process groups need not necessarily have leaders, although they always begin with one.
Sessions are identified by the process group ID of the session leader.
POSIX prohibits the change of the process group ID of a session leader.
The system call setpgid is used to set the process group ID of a process, thereby either joining the process to an existing process group, or creating a new process group within the session of the process with the process becoming the process group leader of the newly created group.[5]
POSIX prohibits the re-use of a process ID where a process group with that identifier still exists (i.e. where the leader of a process group has exited, but other processes in the group still exist).
It thereby guarantees that processes may not accidentally become process group leaders.
The system call kill is capable of directing signals either to individual processes or to process groups.[2]
See also
[edit]- cgroups
- Windows Object Manager, specifically Job objects and associated resource limits[6]
References
[edit]- Single UNIX Specification, Issue 6
- ^
IEEE and The Open Group (2018). "3. Definitions". The Open Group Base Specifications Issue 7. § 296. Retrieved 2020-08-30.
A collection of processes that permits the signaling of related processes.
- ^ a b – System Interfaces Reference, The Single UNIX Specification, Version 5 from The Open Group
- ^
IEEE and The Open Group (2018). "3. Definitions". The Open Group Base Specifications Issue 7. § 343. Retrieved 2020-08-30.
A collection of process groups [...]. Each process group is a member of a session.
- ^ – System Interfaces Reference, The Single UNIX Specification, Version 5 from The Open Group
- ^ – System Interfaces Reference, The Single UNIX Specification, Version 5 from The Open Group
- ^ Karl-Bridge-Microsoft (7 January 2021). "Job Objects - Win32 apps". docs.microsoft.com. Retrieved 2022-08-28.
Further reading
[edit]- McKusick, Marshall Kirk; Neville-Neil, George V. (2004-08-02). "FreeBSD Process Management: Process Groups and Sessions". The Design and Implementation of the FreeBSD Operating System. Addison Wesley. ISBN 0-201-70245-2.
- UNIX Signals and Process Groups