>Number:         9707
>Category:       bin
>Synopsis:       ping6(8) lies about using <sysexits.h>
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 29 22:12:00 2000
>Last-Modified:
>Originator:     matthew green
>Organization:
people's front against (bozotic) www (softwar foundation)
>Release:        <NetBSD-current source date>feb 20
>Environment:
	
System: NetBSD fish-dances.eterna.com.au 1.4T NetBSD 1.4T (_fish_) #10: Fri Mar 17 16:36:55 EST 2000 mrg@fish-dances.eterna.com.au:/var/_fish_ i386


>Description:

	excerpt from ping6(8):

RETURN VALUES
     The ping6 command returns an exit status of zero if at least one response
     was heard from the specified host; a status of two if the transmission
     was successful but no responses were received; or another value (from
     <sysexits.h>) if an error occurred.

	but in reality, the only calls to exit are as following and <sysexit.h>
	is not even included.

ping6.c:                exit(1);
ping6.c:        exit(nreceived == 0);
ping6.c:        exit(1);
ping6.c:        exit(1);

	additionally, there is no place that an exit status of 2 is used.

>How-To-Repeat:

	read ping6(8). be curious why you can't get an exit status of 2 from
	it.  read ping6.c and see why.
>Fix:
	
	not given.  (fix program or docs).

>Audit-Trail:
>Unformatted: