aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2017-03-17 07:55:58 +0100
committerMichael Kerrisk <mtk.manpages@gmail.com>2017-03-17 12:33:58 +0100
commit94e460d409c4e08f5ab87f04bec3dc809d5cd63a (patch)
tree4edff4d60952b93f3c895b16a12c1076a1269e63
parentf0fb21d143950a709ddd68124d26c0094172a218 (diff)
downloadman-pages-94e460d409c4e08f5ab87f04bec3dc809d5cd63a.tar.gz
prctl.2: Explain rationale for use of subreaper processes
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r--man2/prctl.211
1 files changed, 11 insertions, 0 deletions
diff --git a/man2/prctl.2 b/man2/prctl.2
index 633a0eb176..ed374e5862 100644
--- a/man2/prctl.2
+++ b/man2/prctl.2
@@ -184,6 +184,17 @@ and
.BR clone (2).
The setting is preserved across
.BR execve (2).
+
+Establishing a subreaper process is useful in session management frameworks
+where a hierarchical group of processes is managed by a subreaper process
+that needs to be informed when one of the processes\(emfor example,
+a double-forked daemon\(emterminates
+(perhaps so that it can restart that process).
+Some
+.BR init (1)
+frameworks (e.g.,
+.BR systemd (1))
+employ a subreaper process for similar reasons.
.TP
.BR PR_GET_CHILD_SUBREAPER " (since Linux 3.4)"
Return the "child subreaper" setting of the caller,