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

sigpending.2: explain effect of fork() and execve() for pending signal set 

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2008-10-04 06:38:30 +02:00
parent 7acce9fb90
commit a6b7b51147
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
man2/sigpending.2
View File

@ -24,7 +24,7 @@
.\"
.\" 2005-09-15, mtk, Created new page by splitting off from sigaction.2
.\"
.TH SIGPENDING 2 2008-08-29 "Linux" "Linux Programmer's Manual"
.TH SIGPENDING 2 2008-10-04 "Linux" "Linux Programmer's Manual"
.SH NAME
sigpending \- examine pending signals
.SH SYNOPSIS
@ -67,6 +67,12 @@ The set of signals that is pending for a thread
is the union of the set of signals that is pending for that thread
and the set of threads that is peding for the process as a whole; see
.BR signal (7).
A child created via
.BR fork (2)
initially has an empty pending signal set;
the pending signal set is preserved across an
.BR execve (2).
.SH BUGS
In versions of glibc up to and including 2.2.1,
there is a bug in the wrapper function for