2 .\" Copyright (c) 1993 by Thomas Koenig (ig25@rz.uni-karlsruhe.de)
3 .\" and Copyright (c) 2002, 2006 by Michael Kerrisk <mtk.manpages@gmail.com>
4 .\" and Copyright (c) 2008 Linux Foundation, written by Michael Kerrisk
5 .\" <mtk.manpages@gmail.com>
7 .\" %%%LICENSE_START(VERBATIM)
8 .\" Permission is granted to make and distribute verbatim copies of this
9 .\" manual provided the copyright notice and this permission notice are
10 .\" preserved on all copies.
12 .\" Permission is granted to copy and distribute modified versions of this
13 .\" manual under the conditions for verbatim copying, provided that the
14 .\" entire resulting derived work is distributed under the terms of a
15 .\" permission notice identical to this one.
17 .\" Since the Linux kernel and libraries are constantly changing, this
18 .\" manual page may be incorrect or out-of-date. The author(s) assume no
19 .\" responsibility for errors or omissions, or for damages resulting from
20 .\" the use of the information contained herein. The author(s) may not
21 .\" have taken the same level of care in the production of this manual,
22 .\" which is licensed free of charge, as they might when working
25 .\" Formatted or processed versions of this manual, if unaccompanied by
26 .\" the source, must acknowledge the copyright and authors of this work.
29 .\" Modified Sat Jul 24 17:34:08 1993 by Rik Faith (faith@cs.unc.edu)
30 .\" Modified Sun Jan 7 01:41:27 1996 by Andries Brouwer (aeb@cwi.nl)
31 .\" Modified Sun Apr 14 12:02:29 1996 by Andries Brouwer (aeb@cwi.nl)
32 .\" Modified Sat Nov 13 16:28:23 1999 by Andries Brouwer (aeb@cwi.nl)
33 .\" Modified 10 Apr 2002, by Michael Kerrisk <mtk.manpages@gmail.com>
34 .\" Modified 7 Jun 2002, by Michael Kerrisk <mtk.manpages@gmail.com>
35 .\" Added information on real-time signals
36 .\" Modified 13 Jun 2002, by Michael Kerrisk <mtk.manpages@gmail.com>
37 .\" Noted that SIGSTKFLT is in fact unused
38 .\" 2004-12-03, Modified mtk, added notes on RLIMIT_SIGPENDING
39 .\" 2006-04-24, mtk, Added text on changing signal dispositions,
40 .\" signal mask, and pending signals.
42 .\" Added section on system call restarting (SA_RESTART)
43 .\" Added section on stop/cont signals interrupting syscalls.
44 .\" 2008-10-05, mtk: various additions
46 .TH SIGNAL 7 2019-03-06 "Linux" "Linux Programmer's Manual"
48 signal \- overview of signals
50 Linux supports both POSIX reliable signals (hereinafter
51 "standard signals") and POSIX real-time signals.
52 .SS Signal dispositions
53 Each signal has a current
55 which determines how the process behaves when it is delivered
58 The entries in the "Action" column of the table below specify
59 the default disposition for each signal, as follows:
61 Default action is to terminate the process.
63 Default action is to ignore the signal.
65 Default action is to terminate the process and dump core (see
68 Default action is to stop the process.
70 Default action is to continue the process if it is currently stopped.
72 A process can change the disposition of a signal using
76 (The latter is less portable when establishing a signal handler;
80 Using these system calls, a process can elect one of the
81 following behaviors to occur on delivery of the signal:
82 perform the default action; ignore the signal;
83 or catch the signal with a
84 .IR "signal handler" ,
85 a programmer-defined function that is automatically invoked
86 when the signal is delivered.
88 By default, a signal handler is invoked on the
90 It is possible to arrange that the signal handler
91 uses an alternate stack; see
93 for a discussion of how to do this and when it might be useful.
95 The signal disposition is a per-process attribute:
96 in a multithreaded application, the disposition of a
97 particular signal is the same for all threads.
101 inherits a copy of its parent's signal dispositions.
104 the dispositions of handled signals are reset to the default;
105 the dispositions of ignored signals are left unchanged.
107 The following system calls and library functions allow
108 the caller to send a signal:
111 Sends a signal to the calling thread.
114 Sends a signal to a specified process,
115 to all members of a specified process group,
116 or to all processes on the system.
119 Sends a signal to all of the members of a specified process group.
122 Sends a signal to a specified POSIX thread in the same process as
126 Sends a signal to a specified thread within a specific process.
127 (This is the system call used to implement
128 .BR pthread_kill (3).)
131 Sends a real-time signal with accompanying data to a specified process.
132 .SS Waiting for a signal to be caught
133 The following system calls suspend execution of the calling
134 thread until a signal is caught
135 (or an unhandled signal terminates the process):
138 Suspends execution until any signal is caught.
141 Temporarily changes the signal mask (see below) and suspends
142 execution until one of the unmasked signals is caught.
143 .SS Synchronously accepting a signal
144 Rather than asynchronously catching a signal via a signal handler,
145 it is possible to synchronously accept the signal, that is,
146 to block execution until the signal is delivered,
147 at which point the kernel returns information about the
148 signal to the caller.
149 There are two general ways to do this:
152 .BR sigtimedwait (2),
155 suspend execution until one of the signals in a specified
157 Each of these calls returns information about the delivered signal.
160 returns a file descriptor that can be used to read information
161 about signals that are delivered to the caller.
164 from this file descriptor blocks until one of the signals
165 in the set specified in the
167 call is delivered to the caller.
168 The buffer returned by
170 contains a structure describing the signal.
171 .SS Signal mask and pending signals
174 which means that it will not be delivered until it is later unblocked.
175 Between the time when it is generated and when it is delivered
176 a signal is said to be
179 Each thread in a process has an independent
181 which indicates the set of signals that the thread is currently blocking.
182 A thread can manipulate its signal mask using
183 .BR pthread_sigmask (3).
184 In a traditional single-threaded application,
186 can be used to manipulate the signal mask.
190 inherits a copy of its parent's signal mask;
191 the signal mask is preserved across
194 A signal may be generated (and thus pending)
195 for a process as a whole (e.g., when sent using
197 or for a specific thread (e.g., certain signals,
203 consequence of executing a specific machine-language instruction
204 are thread directed, as are signals targeted at a specific thread using
205 .BR pthread_kill (3)).
206 A process-directed signal may be delivered to any one of the
207 threads that does not currently have the signal blocked.
208 If more than one of the threads has the signal unblocked, then the
209 kernel chooses an arbitrary thread to which to deliver the signal.
211 A thread can obtain the set of signals that it currently has pending
214 This set will consist of the union of the set of pending
215 process-directed signals and the set of signals pending for
220 initially has an empty pending signal set;
221 the pending signal set is preserved across an
224 Linux supports the standard signals listed below.
225 The second column of the table indicates which standard (if any)
226 specified the signal: "P1990" indicates that the signal is described
227 in the original POSIX.1-1990 standard;
228 "P2001" indicates that the signal was added in SUSv2 and POSIX.1-2001.
233 Signal Standard Action Comment
234 SIGABRT P1990 Core Abort signal from \fBabort\fP(3)
235 SIGALRM P1990 Term Timer signal from \fBalarm\fP(2)
236 SIGBUS P2001 Core Bus error (bad memory access)
237 SIGCHLD P1990 Ign Child stopped or terminated
238 SIGCLD \- Ign A synonym for \fBSIGCHLD\fP
239 SIGCONT P1990 Cont Continue if stopped
240 SIGEMT \- Term Emulator trap
241 SIGFPE P1990 Core Floating-point exception
242 SIGHUP P1990 Term Hangup detected on controlling terminal
243 or death of controlling process
244 SIGILL P1990 Core Illegal Instruction
245 SIGINFO \- A synonym for \fBSIGPWR\fP
246 SIGINT P1990 Term Interrupt from keyboard
247 SIGIO \- Term I/O now possible (4.2BSD)
248 SIGIOT \- Core IOT trap. A synonym for \fBSIGABRT\fP
249 SIGKILL P1990 Term Kill signal
250 SIGLOST \- Term File lock lost (unused)
251 SIGPIPE P1990 Term Broken pipe: write to pipe with no
252 readers; see \fBpipe\fP(7)
253 SIGPOLL P2001 Term Pollable event (Sys V).
254 Synonym for \fBSIGIO\fP
255 SIGPROF P2001 Term Profiling timer expired
256 SIGPWR \- Term Power failure (System V)
257 SIGQUIT P1990 Core Quit from keyboard
258 SIGSEGV P1990 Core Invalid memory reference
259 SIGSTKFLT \- Term Stack fault on coprocessor (unused)
260 SIGSTOP P1990 Stop Stop process
261 SIGTSTP P1990 Stop Stop typed at terminal
262 SIGSYS P2001 Core Bad system call (SVr4);
263 see also \fBseccomp\fP(2)
264 SIGTERM P1990 Term Termination signal
265 SIGTRAP P2001 Core Trace/breakpoint trap
266 SIGTTIN P1990 Stop Terminal input for background process
267 SIGTTOU P1990 Stop Terminal output for background process
268 SIGUNUSED \- Core Synonymous with \fBSIGSYS\fP
269 SIGURG P2001 Ign Urgent condition on socket (4.2BSD)
270 SIGUSR1 P1990 Term User-defined signal 1
271 SIGUSR2 P1990 Term User-defined signal 2
272 SIGVTALRM P2001 Term Virtual alarm clock (4.2BSD)
273 SIGXCPU P2001 Core CPU time limit exceeded (4.2BSD);
274 see \fBsetrlimit\fP(2)
275 SIGXFSZ P2001 Core File size limit exceeded (4.2BSD);
276 see \fBsetrlimit\fP(2)
277 SIGWINCH \- Ign Window resize signal (4.3BSD, Sun)
284 cannot be caught, blocked, or ignored.
286 Up to and including Linux 2.2, the default behavior for
287 .BR SIGSYS ", " SIGXCPU ", " SIGXFSZ ", "
288 and (on architectures other than SPARC and MIPS)
290 was to terminate the process (without a core dump).
291 (On some other UNIX systems the default action for
292 .BR SIGXCPU " and " SIGXFSZ
293 is to terminate the process without a core dump.)
294 Linux 2.4 conforms to the POSIX.1-2001 requirements for these signals,
295 terminating the process with a core dump.
299 is not specified in POSIX.1-2001, but nevertheless appears
300 on most other UNIX systems,
301 where its default action is typically to terminate
302 the process with a core dump.
305 (which is not specified in POSIX.1-2001) is typically ignored
306 by default on those other UNIX systems where it appears.
309 (which is not specified in POSIX.1-2001) is ignored by default
310 on several other UNIX systems.
312 .SS Queueing and delivery semantics for standard signals
313 If multiple standard signals are pending for a process,
314 the order in which the signals are delivered is unspecified.
316 Standard signals do not queue.
317 If multiple instances of a standard signal are generated while
318 that signal is blocked,
319 then only one instance of the signal is marked as pending
320 (and the signal will be delivered just once when it is unblocked).
321 In the case where a standard signal is already pending, the
325 associated with that signal is not overwritten
326 on arrival of subsequent instances of the same signal.
327 Thus, the process will receive the information
328 associated with the first instance of the signal.
330 .SS Signal numbering for standard signals
331 The numeric value for each signal is given in the table below.
332 As shown in the table, many signals have different numeric values
333 on different architectures.
334 The first numeric value in each table row shows the signal number
335 on x86, ARM, and most other architectures;
336 the second value is for Alpha and SPARC; the third is for MIPS;
337 and the last is for PARISC.
338 A dash (\-) denotes that a signal is absent on the corresponding architecture.
344 Signal x86/ARM Alpha/ MIPS PARISC Notes
346 SIGHUP \01 \01 \01 \01
347 SIGINT \02 \02 \02 \02
348 SIGQUIT \03 \03 \03 \03
349 SIGILL \04 \04 \04 \04
350 SIGTRAP \05 \05 \05 \05
351 SIGABRT \06 \06 \06 \06
352 SIGIOT \06 \06 \06 \06
355 SIGFPE \08 \08 \08 \08
356 SIGKILL \09 \09 \09 \09
363 SIGSTKFLT 16 \- \- \07
374 SIGVTALRM 26 26 28 20
378 SIGPOLL Same as SIGIO
379 SIGPWR 30 29/\- 19 19
380 SIGINFO \- 29/\- \- \-
381 SIGLOST \- \-/29 \- \-
383 SIGUNUSED 31 \- \- 31
394 is no longer defined on any architecture.
398 (synonyms for the same value) on Alpha but
402 .SS Real-time signals
403 Starting with version 2.2,
404 Linux supports real-time signals as originally defined in the POSIX.1b
405 real-time extensions (and now included in POSIX.1-2001).
406 The range of supported real-time signals is defined by the macros
410 POSIX.1-2001 requires that an implementation support at least
412 (8) real-time signals.
414 The Linux kernel supports a range of 33 different real-time
415 signals, numbered 32 to 64.
416 However, the glibc POSIX threads implementation internally uses
417 two (for NPTL) or three (for LinuxThreads) real-time signals
420 and adjusts the value of
422 suitably (to 34 or 35).
423 Because the range of available real-time signals varies according
424 to the glibc threading implementation (and this variation can occur
425 at run time according to the available kernel and glibc),
426 and indeed the range of real-time signals varies across UNIX systems,
428 .IR "never refer to real-time signals using hard-coded numbers" ,
429 but instead should always refer to real-time signals using the notation
431 and include suitable (run-time) checks that
436 Unlike standard signals, real-time signals have no predefined meanings:
437 the entire set of real-time signals can be used for application-defined
440 The default action for an unhandled real-time signal is to terminate the
443 Real-time signals are distinguished by the following:
445 Multiple instances of real-time signals can be queued.
446 By contrast, if multiple instances of a standard signal are delivered
447 while that signal is currently blocked, then only one instance is queued.
449 If the signal is sent using
451 an accompanying value (either an integer or a pointer) can be sent
453 If the receiving process establishes a handler for this signal using the
457 then it can obtain this data via the
461 structure passed as the second argument to the handler.
466 fields of this structure can be used to obtain the PID
467 and real user ID of the process sending the signal.
469 Real-time signals are delivered in a guaranteed order.
470 Multiple real-time signals of the same type are delivered in the order
472 If different real-time signals are sent to a process, they are delivered
473 starting with the lowest-numbered signal.
474 (I.e., low-numbered signals have highest priority.)
475 By contrast, if multiple standard signals are pending for a process,
476 the order in which they are delivered is unspecified.
478 If both standard and real-time signals are pending for a process,
479 POSIX leaves it unspecified which is delivered first.
480 Linux, like many other implementations, gives priority
481 to standard signals in this case.
483 According to POSIX, an implementation should permit at least
484 .B _POSIX_SIGQUEUE_MAX
485 (32) real-time signals to be queued to
487 However, Linux does things differently.
488 In kernels up to and including 2.6.7, Linux imposes
489 a system-wide limit on the number of queued real-time signals
491 This limit can be viewed and (with privilege) changed via the
492 .I /proc/sys/kernel/rtsig-max
495 .IR /proc/sys/kernel/rtsig-nr ,
496 can be used to find out how many real-time signals are currently queued.
497 In Linux 2.6.8, these
499 interfaces were replaced by the
501 resource limit, which specifies a per-user limit for queued
506 The addition of real-time signals required the widening
507 of the signal set structure
510 Consequently, various system calls were superseded by new system calls
511 that supported the larger signal sets.
512 The old and new system calls are as follows:
516 Linux 2.0 and earlier Linux 2.2 and later
517 \fBsigaction\fP(2) \fBrt_sigaction\fP(2)
518 \fBsigpending\fP(2) \fBrt_sigpending\fP(2)
519 \fBsigprocmask\fP(2) \fBrt_sigprocmask\fP(2)
520 \fBsigreturn\fP(2) \fBrt_sigreturn\fP(2)
521 \fBsigsuspend\fP(2) \fBrt_sigsuspend\fP(2)
522 \fBsigtimedwait\fP(2) \fBrt_sigtimedwait\fP(2)
525 .SS Interruption of system calls and library functions by signal handlers
526 If a signal handler is invoked while a system call or library
527 function call is blocked, then either:
529 the call is automatically restarted after the signal handler returns; or
531 the call fails with the error
534 Which of these two behaviors occurs depends on the interface and
535 whether or not the signal handler was established using the
539 The details vary across UNIX systems;
540 below, the details for Linux.
542 If a blocked call to one of the following interfaces is interrupted
543 by a signal handler, then the call is automatically restarted
544 after the signal handler returns if the
546 flag was used; otherwise the call fails with the error
548 .\" The following system calls use ERESTARTSYS,
549 .\" so that they are restartable
557 calls on "slow" devices.
558 A "slow" device is one where the I/O call may block for an
559 indefinite time, for example, a terminal, pipe, or socket.
560 If an I/O call on a slow device has already transferred some
561 data by the time it is interrupted by a signal handler,
562 then the call will return a success status
563 (normally, the number of bytes transferred).
564 Note that a (local) disk is not a slow device according to this definition;
565 I/O operations on disk devices are not interrupted by signals.
568 if it can block (e.g., when opening a FIFO; see
579 .\" If a timeout (setsockopt()) is in effect on the socket, then these
580 .\" system calls switch to using EINTR. Consequently, they and are not
581 .\" automatically restarted, and they show the stop/cont behavior
582 .\" described below. (Verified from 2.6.26 source, and by experiment; mtk)
593 .\" FIXME What about sendmmsg()?
594 unless a timeout has been set on the socket (see below).
596 File locking interfaces:
606 POSIX message queue interfaces:
608 .BR mq_timedreceive (3),
611 .BR mq_timedsend (3).
616 .\" commit 72c1bbf308c75a136803d2d76d0e18258be14c7a
617 beforehand, always failed with
622 .BR pthread_mutex_lock (3),
623 .BR pthread_cond_wait (3),
627 .BR FUTEX_WAIT_BITSET .
629 POSIX semaphore interfaces:
632 .BR sem_timedwait (3)
634 .\" as a consequence of the 2.6.22 changes in the futex() implementation
635 beforehand, always failed with
643 .\" commit 1ca39ab9d21ac93f94b9e3eb364ea9a5cf2aba06
644 beforehand, always failed with
647 The following interfaces are never restarted after
648 being interrupted by a signal handler,
649 regardless of the use of
651 they always fail with the error
653 when interrupted by a signal handler:
654 .\" These are the system calls that give EINTR or ERESTARTNOHAND
655 .\" on interruption by a signal handler.
657 "Input" socket interfaces, when a timeout
659 has been set on the socket using
665 (also with a non-NULL
671 "Output" socket interfaces, when a timeout
673 has been set on the socket using
680 .\" FIXME What about sendmmsg()?
682 Interfaces used to wait for signals:
685 .BR sigtimedwait (2),
689 File descriptor multiplexing interfaces:
698 System V IPC interfaces:
699 .\" On some other systems, SA_RESTART does restart these system calls
707 .BR clock_nanosleep (2),
712 .BR io_getevents (2).
716 function is also never restarted if interrupted by a handler,
717 but gives a success return: the number of seconds remaining to sleep.
718 .SS Interruption of system calls and library functions by stop signals
719 On Linux, even in the absence of signal handlers,
720 certain blocking interfaces can fail with the error
722 after the process is stopped by one of the stop signals
725 This behavior is not sanctioned by POSIX.1, and doesn't occur
728 The Linux interfaces that display this behavior are:
730 "Input" socket interfaces, when a timeout
732 has been set on the socket using
738 (also with a non-NULL
744 "Output" socket interfaces, when a timeout
746 has been set on the socket using
752 .\" FIXME What about sendmmsg()?
764 .BR sigtimedwait (2),
767 Linux 3.7 and earlier:
772 .\" commit 1ca39ab9d21ac93f94b9e3eb364ea9a5cf2aba06
774 Linux 2.6.21 and earlier:
777 .BR sem_timedwait (3),
780 Linux 2.6.8 and earlier:
784 Linux 2.4 and earlier:
787 POSIX.1, except as noted.
788 .\" It must be a *very* long time since this was true:
793 .\" have the same value.
794 .\" The latter is commented out in the kernel source, but
795 .\" the build process of some software still thinks that
799 For a discussion of async-signal-safe functions, see
800 .BR signal-safety (7).
803 .I /proc/[pid]/task/[tid]/status
804 file contains various fields that show the signals
805 that a thread is blocking
811 (The set of signals that are caught or ignored will be the same
812 across all threads in a process.)
813 Other fields show the set of pending signals that are directed to the thread
815 as well as the set of pending signals that are directed
816 to the process as a whole
818 The corresponding fields in
819 .I /proc/[pid]/status
820 show the information for the main thread.
829 .BR restart_syscall (2),
830 .BR rt_sigqueueinfo (2),
847 .BR pthread_sigqueue (3),