o From kern_prot.c::p_cansignal():
UNIX signalling semantics require that processes in the same session always be able to deliver SIGCONT to one another, overriding the remaining protections. Fix SIGCONT special case description similar to rev. 1.22 kill.2. PR: docs/58710 Submitted by: Ryan Younce MFC after: 2 weeks
This commit is contained in:
parent
6e4da6de20
commit
5c35171af3
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=163197
@ -32,7 +32,7 @@
|
||||
.\" @(#)killpg.2 8.1 (Berkeley) 6/2/93
|
||||
.\" $FreeBSD$
|
||||
.\"
|
||||
.Dd June 2, 1993
|
||||
.Dd October 10, 2006
|
||||
.Dt KILLPG 2
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -66,7 +66,7 @@ The sending process and members of the process group must
|
||||
have the same effective user ID, or
|
||||
the sender must be the super-user.
|
||||
As a single special case the continue signal SIGCONT may be sent
|
||||
to any process that is a descendant of the current process.
|
||||
to any process with the same session ID as the caller.
|
||||
.Sh RETURN VALUES
|
||||
.Rv -std killpg
|
||||
.Sh ERRORS
|
||||
|
Loading…
Reference in New Issue
Block a user