From c20f599a534a319873b5edfeef73a5f100a6add6 Mon Sep 17 00:00:00 2001 From: kensmith Date: Fri, 24 Oct 2003 21:20:26 +0000 Subject: - fix description of what processes SIGCONT can be sent to PR: docs/58413 Reviewed by: rwatson Approved by: blackend (mentor) --- lib/libc/sys/kill.2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lib/libc') diff --git a/lib/libc/sys/kill.2 b/lib/libc/sys/kill.2 index b0a4fde..5164066 100644 --- a/lib/libc/sys/kill.2 +++ b/lib/libc/sys/kill.2 @@ -72,7 +72,7 @@ the real or effective user ID of the receiving process must match that of the sending process or the user must have appropriate privileges (such as given by a set-user-ID program or the user is the super-user). A single exception is the signal SIGCONT, which may always be sent -to any descendant of the current process. +to any process with the same session ID as the caller. .Bl -tag -width Ds .It \&If Fa pid No \&is greater than zero : The -- cgit v1.1