sigaction.2: explain semantics of signal disposition during fork() and execve()

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2008-10-04 07:49:53 +02:00
parent 0178675542
commit 0ac0def44d
1 changed files with 9 additions and 2 deletions

View File

@ -40,7 +40,7 @@
.\" 2005-09-15, mtk, split sigpending(), sigprocmask(), sigsuspend()
.\" out of this page into separate pages.
.\"
.TH SIGACTION 2 2008-08-29 "Linux" "Linux Programmer's Manual"
.TH SIGACTION 2 2008-10-04 "Linux" "Linux Programmer's Manual"
.SH NAME
sigaction \- examine and change a signal action
.SH SYNOPSIS
@ -549,7 +549,14 @@ which cannot be caught or ignored.
POSIX.1-2001, SVr4.
.\" SVr4 does not document the EINTR condition.
.SH NOTES
.PP
The child created via
.BR fork (2)
inherits a copy of its parent's signal dispositions.
During an
.BR execve (2),
the dispositions of handled signals are reset to the default;
the dispositions of ignored signals are left unchanged.
According to POSIX, the behavior of a process is undefined after it
ignores a
.BR SIGFPE ,