From 0ac0def44d86ee205794f767dd0c4a8772e052ec Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Sat, 4 Oct 2008 07:49:53 +0200 Subject: [PATCH] sigaction.2: explain semantics of signal disposition during fork() and execve() Signed-off-by: Michael Kerrisk --- man2/sigaction.2 | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/man2/sigaction.2 b/man2/sigaction.2 index b09ff768a..b23e6afd0 100644 --- a/man2/sigaction.2 +++ b/man2/sigaction.2 @@ -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 ,