From 7edfdaca06f086b785b25a61ded5840d2af6866c Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Sat, 12 Jun 2010 14:53:29 +0200 Subject: [PATCH] signal.7: Make a clearer statement about nonportable aspect of signal(2) Make a clearer statement that signal(2) is less portable for establishing a signal handler. Reported-by: Reuben Thomas Signed-off-by: Michael Kerrisk --- man7/signal.7 | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/man7/signal.7 b/man7/signal.7 index bc1e72ecb..d67c8937f 100644 --- a/man7/signal.7 +++ b/man7/signal.7 @@ -41,7 +41,7 @@ .\" Added section on stop/cont signals interrupting syscalls. .\" 2008-10-05, mtk: various additions .\" -.TH SIGNAL 7 2010-02-03 "Linux" "Linux Programmer's Manual" +.TH SIGNAL 7 2010-06-12 "Linux" "Linux Programmer's Manual" .SH NAME signal \- overview of signals .SH DESCRIPTION @@ -69,8 +69,12 @@ Default action is to continue the process if it is currently stopped. .PP A process can change the disposition of a signal using .BR sigaction (2) -or (less portably) +or .BR signal (2). +(The latter is less portable when establishing a signal handler; +see +.BR signal (2) +for details.) Using these system calls, a process can elect one of the following behaviors to occur on delivery of the signal: perform the default action; ignore the signal;