Remove non-existing error condition.
Just like kill(2), it is impossible for killpg(0, ...) to fail with ESRCH, as a process always has a process group. Discussed on: arch@ MFC after: 1 week
This commit is contained in:
parent
246e44956e
commit
effed41a0b
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=233012
@ -28,7 +28,7 @@
|
||||
.\" @(#)killpg.2 8.1 (Berkeley) 6/2/93
|
||||
.\" $FreeBSD$
|
||||
.\"
|
||||
.Dd October 10, 2006
|
||||
.Dd March 15, 2012
|
||||
.Dt KILLPG 2
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -79,9 +79,6 @@ is not a valid signal number.
|
||||
.It Bq Er ESRCH
|
||||
No process can be found in the process group specified by
|
||||
.Fa pgrp .
|
||||
.It Bq Er ESRCH
|
||||
The process group was given as 0
|
||||
but the sending process does not have a process group.
|
||||
.It Bq Er EPERM
|
||||
The sending process is not the super-user and one or more
|
||||
of the target processes has an effective user ID different from that
|
||||
|
Loading…
Reference in New Issue
Block a user