Subject: Re: bin/21933: pkill doesn't behave as documented
To: None <gnats-admin@netbsd.org, netbsd-bugs@netbsd.org>
From: Christian Biere <christianbiere@gmx.de>
List: netbsd-bugs
Date: 09/10/2005 18:50:03
The following reply was made to PR bin/21933; it has been noted by GNATS.

From: Christian Biere <christianbiere@gmx.de>
To: Julio Merino <jmmv@menta.net>
Cc: gnats-bugs@netbsd.org
Subject: Re: bin/21933: pkill doesn't behave as documented
Date: Sat, 10 Sep 2005 20:49:38 +0200

 Julio Merino wrote:
 > On Thu, 19 Jun 2003 23:22:12 +0200
 > Christian Biere <christianbiere@gmx.de> wrote:
  
 > > -		err(STATUS_ERROR, "signalling pid %d", (int)kp->p_pid);
 > > +		warn("signalling pid %d", (int)kp->p_pid);
 
 This looks fixed in the current pkill sources.
  
 > Which error code should return the program then?
  
 >      0    One or more processes were matched.
 >      1    No processes were matched.
 >      2    Invalid options were specified on the command line.
 >      3    An internal error occurred.
  
 > It will always return 0 or 1 instead of 3.  Is this right?
 
 Yes. However, pkill exits with 3 instead of 2 in usage().
 
 -- 
 Christian