Date: Thu, 23 Oct 2003 04:19:09 -0400 (EDT) From: Ryan Younce <ryan@tribug.org> To: FreeBSD-gnats-submit@FreeBSD.org Subject: docs/58413: kill(2) contains an error regarding sending SIGCONT Message-ID: <20031023081909.C849911532@turing.vangyzen.net> Resent-Message-ID: <200310230800.h9N80TLQ074285@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 58413 >Category: docs >Synopsis: kill(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 23 01:00:27 PDT 2003 >Closed-Date: >Last-Modified: >Originator: Ryan Younce >Release: FreeBSD 5.1-BETA i386 >Organization: >Environment: System: FreeBSD turing.vangyzen.net 5.1-BETA FreeBSD 5.1-BETA #0: Tue May 6 12:07:36 GMT 2003 root@hollin.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC i386 >Description: The kill(2) manual page for CURRENT states "A single exception is the signal SIGCONT, which may always be sent to any descendent of the current process." In CURRENT, however, this provision is false: the process can send SIGCONT to any other process in the caller's session (to align with POSIX). Behavior has been tested, also reference: p_cansignal() function in /sys/kern/kern_prot.c >How-To-Repeat: man 2 kill >Fix: Change sentence in question to: "A single exception is the signal SIGCONT, which may always be sent to any process with the same session ID as the caller." or something similar. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031023081909.C849911532>