diff options
Diffstat (limited to 'man2/signal.2')
-rw-r--r-- | man2/signal.2 | 60 |
1 files changed, 30 insertions, 30 deletions
diff --git a/man2/signal.2 b/man2/signal.2 index 5e84f40c3..132f2c138 100644 --- a/man2/signal.2 +++ b/man2/signal.2 @@ -34,7 +34,7 @@ the behavior of varies across UNIX versions, and has also varied historically across different versions of Linux. \fBAvoid its use\fP: use -.BR sigaction (2) +.MR sigaction 2 instead. See \fIPortability\fP below. .P @@ -61,7 +61,7 @@ then the signal is ignored. If the disposition is set to .BR SIG_DFL , then the default action associated with the signal (see -.BR signal (7)) +.MR signal 7 ) occurs. .TP * @@ -133,7 +133,7 @@ to establish a signal handler vary across systems .B do not use it for this purpose. .P POSIX.1 solved the portability mess by specifying -.BR sigaction (2), +.MR sigaction 2 , which provides explicit control of the semantics when a signal handler is invoked; use that interface instead of .BR signal (). @@ -149,7 +149,7 @@ the disposition of the signal would be reset to .BR SIG_DFL , and the system did not block delivery of further instances of the signal. This is equivalent to calling -.BR sigaction (2) +.MR sigaction 2 with the following flags: .P .in +4n @@ -175,9 +175,9 @@ and further instances of the signal are blocked from being delivered while the handler is executing. Furthermore, certain blocking system calls are automatically restarted if interrupted by a signal handler (see -.BR signal (7)). +.MR signal 7 ). The BSD semantics are equivalent to calling -.BR sigaction (2) +.MR sigaction 2 with the following flags: .P .in +4n @@ -196,7 +196,7 @@ By default, in glibc 2 and later, the .BR signal () wrapper function does not invoke the kernel system call. Instead, it calls -.BR sigaction (2) +.MR sigaction 2 using flags that supply BSD semantics. This default behavior is provided as long as a suitable feature test macro is defined: @@ -205,7 +205,7 @@ on glibc 2.19 and earlier or .B _DEFAULT_SOURCE in glibc 2.19 and later. (By default, these macros are defined; see -.BR feature_test_macros (7) +.MR feature_test_macros 7 for details.) If such a feature test macro is not defined, then .BR signal () @@ -237,9 +237,9 @@ ignores a or .B SIGSEGV signal that was not generated by -.BR kill (2) +.MR kill 2 or -.BR raise (3). +.MR raise 3 . Integer division by zero has undefined result. On some architectures it will generate a .B SIGFPE @@ -249,32 +249,32 @@ signal. Ignoring this signal might lead to an endless loop. .P See -.BR sigaction (2) +.MR sigaction 2 for details on what happens when the disposition .B SIGCHLD is set to .BR SIG_IGN . .P See -.BR signal\-safety (7) +.MR signal\-safety 7 for a list of the async-signal-safe functions that can be safely called from inside a signal handler. .SH SEE ALSO -.BR kill (1), -.BR alarm (2), -.BR kill (2), -.BR pause (2), -.BR sigaction (2), -.BR signalfd (2), -.BR sigpending (2), -.BR sigprocmask (2), -.BR sigsuspend (2), -.BR bsd_signal (3), -.BR killpg (3), -.BR raise (3), -.BR siginterrupt (3), -.BR sigqueue (3), -.BR sigsetops (3), -.BR sigvec (3), -.BR sysv_signal (3), -.BR signal (7) +.MR kill 1 , +.MR alarm 2 , +.MR kill 2 , +.MR pause 2 , +.MR sigaction 2 , +.MR signalfd 2 , +.MR sigpending 2 , +.MR sigprocmask 2 , +.MR sigsuspend 2 , +.MR bsd_signal 3 , +.MR killpg 3 , +.MR raise 3 , +.MR siginterrupt 3 , +.MR sigqueue 3 , +.MR sigsetops 3 , +.MR sigvec 3 , +.MR sysv_signal 3 , +.MR signal 7 |