LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

Small wording change under NOTES to clarify 

what happends when a process sends a signal to itself.
See Debian bug 350236.
This commit is contained in:
Michael Kerrisk 2006-02-03 03:46:54 +00:00
parent a5a997ca09
commit cbea10b39a
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
man2/kill.2
View File

@ -116,10 +116,11 @@ Linux allows a process to signal itself, but on Linux the call
\fIkill(\-1,sig)\fP does not signal the current process.
.LP
POSIX 1003.1-2003 requires that if a process sends a signal to itself,
and that process does not have the signal blocked, and no other thread
and the sending thread does not have the signal blocked,
and no other thread
has it unblocked or is waiting for it in \fIsigwait\fP(), at least one
unblocked signal must be delivered to the sending thread before the
call of \fIkill\fP() returns.
\fIkill\fP().
.SH BUGS
In 2.6 kernels up to and including 2.6.7,
there was a bug that meant that when sending signals to a process group,