bin/75156: sigismember detects errors, contradicting documentation

[Thomas Quinot]

>Number:         75156
>Category:       bin
>Synopsis:       sigismember detects errors, contradicting documentation
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Dec 16 16:40:16 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Thomas Quinot
>Release:        FreeBSD 5.2-CURRENT i386
>Organization:
>Environment:
System: FreeBSD malevil.act-europe.fr 5.2-CURRENT FreeBSD 5.2-CURRENT #1: Mon Aug 2 16:09:18 CEST 2004 root at alexandria.act-europe.fr:/usr/obj/usr/src/HEAD/sys/ADACORE i386


	
>Description:
	man sigismember indicates:

RETURN VALUES
     The sigismember() function returns 1 if the signal is a member of the
     set, 0 otherwise.  The other functions return 0.

ERRORS
     Currently no errors are detected.

     but implementation contains:

        if (signo <= 0 || signo > _SIG_MAXSIG) {
                errno = EINVAL;
                return (-1);
        }

>How-To-Repeat:
	
>Fix:
	Documentation and implementation should be made consistent.
	It appears that the FreeBSD behaviour is consistent with what
	is done on most other UNIX platforms, with the notable exception
	of MacOS X, so the correct course of action is probably to fix
	the man page (but we should first check with relevant standards
	that this is indeed conformant).
>Release-Note:
>Audit-Trail:
>Unformatted: