diff options
Diffstat (limited to 'man2/sigaction.2')
| -rw-r--r-- | man2/sigaction.2 | 136 |
1 files changed, 68 insertions, 68 deletions
diff --git a/man2/sigaction.2 b/man2/sigaction.2 index 0bbc44bd5..75b14ba07 100644 --- a/man2/sigaction.2 +++ b/man2/sigaction.2 @@ -42,7 +42,7 @@ Standard C library .P .RS -4 Feature Test Macro Requirements for glibc (see -.BR feature_test_macros (7)): +.MR feature_test_macros 7 ): .RE .P .BR sigaction (): @@ -60,7 +60,7 @@ The system call is used to change the action taken by a process on receipt of a specific signal. (See -.BR signal (7) +.MR signal 7 for an overview of signals.) .P .I signum @@ -108,7 +108,7 @@ field is not intended for application use. .I sa_restorer field.) Some further details of the purpose of this field can be found in -.BR sigreturn (2). +.MR sigreturn 2 . .P .I sa_handler specifies the action to be associated with @@ -163,7 +163,7 @@ or or resume (i.e., they receive .BR SIGCONT ) (see -.BR wait (2)). +.MR wait 2 ). This flag is meaningful only when establishing a handler for .BR SIGCHLD . .TP @@ -175,7 +175,7 @@ is .BR SIGCHLD , do not transform children into zombies when they terminate. See also -.BR waitpid (2). +.MR waitpid 2 . This flag is meaningful only when establishing a handler for .BR SIGCHLD , or when setting that signal's disposition to @@ -206,7 +206,7 @@ is an obsolete, nonstandard synonym for this flag. .TP .B SA_ONSTACK Call the signal handler on an alternate signal stack provided by -.BR sigaltstack (2). +.MR sigaltstack 2 . If an alternate stack is not available, the default stack will be used. This flag is meaningful only when establishing a signal handler. .TP @@ -222,7 +222,7 @@ Provide behavior compatible with BSD signal semantics by making certain system calls restartable across signals. This flag is meaningful only when establishing a signal handler. See -.BR signal (7) +.MR signal 7 for a discussion of system call restarting. .TP .B SA_RESTORER @@ -231,7 +231,7 @@ This flag is used by C libraries to indicate that the .I sa_restorer field contains the address of a "signal trampoline". See -.BR sigreturn (2) +.MR sigreturn 2 for more details. .TP .BR SA_SIGINFO " (since Linux 2.2)" @@ -321,13 +321,13 @@ structure, cast to \fIvoid\ *\fP. The structure pointed to by this field contains signal context information that was saved on the user-space stack by the kernel; for details, see -.BR sigreturn (2). +.MR sigreturn 2 . Further information about the .I ucontext_t structure can be found in -.BR getcontext (3) +.MR getcontext 3 and -.BR signal (7). +.MR signal 7 . Commonly, the handler function doesn't make any use of the third argument. .P The @@ -389,18 +389,18 @@ The rest of the struct may be a union, so that one should read only the fields that are meaningful for the given signal: .IP \[bu] 3 Signals sent with -.BR kill (2) +.MR kill 2 and -.BR sigqueue (3) +.MR sigqueue 3 fill in .IR si_pid " and " si_uid . In addition, signals sent with -.BR sigqueue (3) +.MR sigqueue 3 fill in .IR si_int " and " si_ptr with the values specified by the sender of the signal; see -.BR sigqueue (3) +.MR sigqueue 3 for more details. .IP \[bu] Signals sent by POSIX.1b timers (since Linux 2.6) fill in @@ -411,24 +411,24 @@ The .I si_timerid field is an internal ID used by the kernel to identify the timer; it is not the same as the timer ID returned by -.BR timer_create (2). +.MR timer_create 2 . The .I si_overrun field is the timer overrun count; this is the same information as is obtained by a call to -.BR timer_getoverrun (2). +.MR timer_getoverrun 2 . These fields are nonstandard Linux extensions. .IP \[bu] Signals sent for message queue notification (see the description of .B SIGEV_SIGNAL in -.BR mq_notify (3)) +.MR mq_notify 3 ) fill in .IR si_int / si_ptr , with the .I sigev_value supplied to -.BR mq_notify (3); +.MR mq_notify 3 ; .IR si_pid , with the process ID of the message sender; and .IR si_uid , @@ -456,16 +456,16 @@ and .I si_stime contain the user and system CPU time used by the child process; these fields do not include the times used by waited-for children (unlike -.BR getrusage (2) +.MR getrusage 2 and -.BR times (2)). +.MR times 2 ). Up to Linux 2.6, and since Linux 2.6.27, these fields report CPU time in units of .IR sysconf(_SC_CLK_TCK) . In Linux 2.6 kernels before Linux 2.6.27, a bug meant that these fields reported time in units of the (configurable) system jiffy (see -.BR time (7)). +.MR time 7 ). .\" FIXME . .\" When si_utime and si_stime where originally implemented, the .\" measurement unit was HZ, which was the same as clock ticks @@ -512,7 +512,7 @@ contains When .B SIGTRAP is delivered in response to a -.BR ptrace (2) +.MR ptrace 2 event (PTRACE_EVENT_foo), .I si_addr is not populated, but @@ -522,7 +522,7 @@ and are populated with the respective process ID and user ID responsible for delivering the trap. In the case of -.BR seccomp (2), +.MR seccomp 2 , the tracee will be shown as delivering the event. .B BUS_MCEERR_* and @@ -556,14 +556,14 @@ The event is a bit mask containing the same values as are filled in the .I revents field by -.BR poll (2). +.MR poll 2 . The .I si_fd field indicates the file descriptor for which the I/O event occurred; for further details, see the description of .B F_SETSIG in -.BR fcntl (2). +.MR fcntl 2 . .IP \[bu] .BR SIGSYS , generated (since Linux 3.5) @@ -576,7 +576,7 @@ fills in .IR si_arch , .IR si_errno , and other fields as described in -.BR seccomp (2). +.MR seccomp 2 . .\" .SS The si_code field @@ -589,7 +589,7 @@ argument that is passed to a signal handler is a value (not a bit mask) indicating why this signal was sent. For a -.BR ptrace (2) +.MR ptrace 2 event, .I si_code will contain @@ -637,20 +637,20 @@ for any signal, along with the reason that the signal was generated. .RS 4 .TP .B SI_USER -.BR kill (2). +.MR kill 2 . .TP .B SI_KERNEL Sent by the kernel. .TP .B SI_QUEUE -.BR sigqueue (3). +.MR sigqueue 3 . .TP .B SI_TIMER POSIX timer expired. .TP .BR SI_MESGQ " (since Linux 2.6.6)" POSIX message queue state changed; see -.BR mq_notify (3). +.MR mq_notify 3 . .TP .B SI_ASYNCIO AIO completed. @@ -665,9 +665,9 @@ fills in as described below). .TP .BR SI_TKILL " (since Linux 2.4.19)" -.BR tkill (2) +.MR tkill 2 or -.BR tgkill (2). +.MR tgkill 2 . .\" SI_DETHREAD is defined in Linux 2.6.9 sources, but isn't implemented .\" It appears to have been an idea that was tried during 2.5.6 .\" through to Linux 2.5.24 and then was backed out. @@ -758,7 +758,7 @@ Failed address bound checks. .\" commit cd0ea35ff5511cde299a61c21a95889b4a71464e Access was denied by memory protection keys. See -.BR pkeys (7). +.MR pkeys 7 . The protection key which applied to this access is available via .IR si_pkey . .RE @@ -867,7 +867,7 @@ signal: .TP .BR SYS_SECCOMP " (since Linux 3.5)" Triggered by a -.BR seccomp (2) +.MR seccomp 2 filter rule. .RE .SS Dynamically probing for flag bit support @@ -951,7 +951,7 @@ gives an error on attempts to change the disposition of the two real-time signals used internally by the NPTL threading implementation. See -.BR nptl (7) +.MR nptl 7 for details. .P On architectures where the signal trampoline resides in the C library, @@ -965,7 +965,7 @@ flag in the .I act.sa_flags field. See -.BR sigreturn (2). +.MR sigreturn 2 . .P The original Linux system call was named .BR sigaction (). @@ -1007,14 +1007,14 @@ to POSIX.1-2001 and later allow this possibility, so that ignoring .B SIGCHLD can be used to prevent the creation of zombies (see -.BR wait (2)). +.MR wait 2 ). Nevertheless, the historical BSD and System\ V behaviors for ignoring .B SIGCHLD differ, so that the only completely portable method of ensuring that terminated children do not become zombies is to catch the .B SIGCHLD signal and perform a -.BR wait (2) +.MR wait 2 or similar. .P POSIX.1-1990 specified only @@ -1048,10 +1048,10 @@ allowed the receipt of any signal, not just the one we are installing settings). .SH NOTES A child created via -.BR fork (2) +.MR fork 2 inherits a copy of its parent's signal dispositions. During an -.BR execve (2), +.MR execve 2 , the dispositions of handled signals are reset to the default; the dispositions of ignored signals are left unchanged. .P @@ -1062,9 +1062,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 @@ -1086,11 +1086,11 @@ It is not possible to block Attempts to do so are silently ignored. .P See -.BR sigsetops (3) +.MR sigsetops 3 for details on manipulating signal sets. .P See -.BR signal\-safety (7) +.MR signal\-safety 7 for a list of the async-signal-safe functions that can be safely called inside from inside a signal handler. .\" @@ -1131,7 +1131,7 @@ This bug was fixed in Linux 2.6.14. .\" commit 69be8f189653cd81aae5a74e26615b12871bb72e .SH EXAMPLES See -.BR mprotect (2). +.MR mprotect 2 . .SS Probing for flag support The following example program exits with status .B EXIT_SUCCESS @@ -1179,25 +1179,25 @@ main(void) .EE .\" SRC END .SH SEE ALSO -.BR kill (1), -.BR kill (2), -.BR pause (2), -.BR pidfd_send_signal (2), -.BR restart_syscall (2), -.BR seccomp (2), -.BR sigaltstack (2), -.BR signal (2), -.BR signalfd (2), -.BR sigpending (2), -.BR sigprocmask (2), -.BR sigreturn (2), -.BR sigsuspend (2), -.BR wait (2), -.BR killpg (3), -.BR raise (3), -.BR siginterrupt (3), -.BR sigqueue (3), -.BR sigsetops (3), -.BR sigvec (3), -.BR core (5), -.BR signal (7) +.MR kill 1 , +.MR kill 2 , +.MR pause 2 , +.MR pidfd_send_signal 2 , +.MR restart_syscall 2 , +.MR seccomp 2 , +.MR sigaltstack 2 , +.MR signal 2 , +.MR signalfd 2 , +.MR sigpending 2 , +.MR sigprocmask 2 , +.MR sigreturn 2 , +.MR sigsuspend 2 , +.MR wait 2 , +.MR killpg 3 , +.MR raise 3 , +.MR siginterrupt 3 , +.MR sigqueue 3 , +.MR sigsetops 3 , +.MR sigvec 3 , +.MR core 5 , +.MR signal 7 |