From effed41a0b97528b5c8539eba41580e64cbe6aed Mon Sep 17 00:00:00 2001
From: Ed Schouten <ed@FreeBSD.org>
Date: Thu, 15 Mar 2012 21:19:50 +0000
Subject: [PATCH] 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
---
 lib/libc/compat-43/killpg.2 | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/lib/libc/compat-43/killpg.2 b/lib/libc/compat-43/killpg.2
index 6793e41d526..b23b773ef50 100644
--- a/lib/libc/compat-43/killpg.2
+++ b/lib/libc/compat-43/killpg.2
@@ -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