d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove non-existing error condition.

Browse Source 
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:
Ed Schouten 2012-03-15 21:19:50 +00:00
parent 246e44956e
commit effed41a0b
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=233012
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
lib/libc/compat-43/killpg.2
View File

@ -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