From bfc592db67ff4749542f1b374c3ae5c99ba84b3a Mon Sep 17 00:00:00 2001 From: Dave Martin Date: Tue, 12 May 2020 17:36:53 +0100 Subject: [PATCH] prctl.2: Work around bogus constant "maxsig" in PR_SET_PDEATHSIG The description of PR_SET_PDEATHSIG refers to "maxsig", which is apparently intended to stand for the maximum defined signal number. maxsig seems not to be a thing, even in the kernel. Reword to use the standard constant NSIG. (Discussion of SIGRTMIN and SIGRTMAX seems out of scope here, and anyway is not relevant to the kernel.) Signed-off-by: Dave Martin Signed-off-by: Michael Kerrisk --- man2/prctl.2 | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/man2/prctl.2 b/man2/prctl.2 index 15a0b2940..6d61a8707 100644 --- a/man2/prctl.2 +++ b/man2/prctl.2 @@ -954,7 +954,9 @@ will operate in the privilege-restricting mode described above. .BR PR_SET_PDEATHSIG " (since Linux 2.1.57)" Set the parent-death signal of the calling process to \fIarg2\fP (either a signal value -in the range 1..maxsig, or 0 to clear). +in the range 1 .. +.BR NSIG " \-" +1, or 0 to clear). This is the signal that the calling process will get when its parent dies. .IP