docs/58710: killpg(2) contains an error regarding sending SIGCONT

[Ryan Younce]

>Number:         58710
>Category:       docs
>Synopsis:       killpg(2) contains an error regarding sending SIGCONT
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 30 00:40:08 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Ryan Younce
>Release:        FreeBSD 5.1-RELEASE i386
>Organization:
>Environment:
FreeBSD kara 5.1-RELEASE FreeBSD 5.1-RELEASE #3: Mon Oct  6 22:31:51 GMT 2003     root at kara:/usr/src/sys/i386/compile/KARA  i386

>Description:

	This is akin to PR docs/58413.

	The killpg(2) manual page in /usr/src/lib/libc/compat-43/killpg.2
	has the same error the kill(2) manpage had before the commit for
	the aforementioned PR, specifically the text:

	"As a single special case the continue signal SIGCONT may be sent
	to any process that is a descendant of the current process."

	This is incorrect:  as in the case for kill(2), SIGCONT may be
	sent, regardless of credentials, to any process in the same
	session; it is neither sufficient nor necessary for the recipient
	to be a descendent if user IDs differ.

	Since killpg() relies on kill(), which relies on killpg1() in
	/sys/kern/kern_sig.c, which relies on p_cansignal() in
	/sys/kern/kern_prot.c, the semantics are the same.  This has 
	also been tested.

>How-To-Repeat:

	man 2 killpg

>Fix:

	Change sentence in question to:

	"As a single special case the continue signal SIGCONT may be sent
	to any process with the same session ID as the caller.
>Release-Note:
>Audit-Trail:
>Unformatted: