NAME

signal - 有效信號(hào)的清單

描述 (DESCRIPTION)

下面 列出 Linux 支持的 信號(hào). 某些 信號(hào) 依賴(lài)于 體系結(jié)構(gòu)(architecture).

首先, POSIX.1 描述了 下列 信號(hào).

下面的 信號(hào) 定義 在 SUSv2 中, 而 POSIX.1 沒(méi)有 定義.

(這里的 SIGSYS, SIGXCPU, SIGXFSZ, 以及 某些 系統(tǒng)上 的 SIGBUS, Linux 的 缺省動(dòng)作 (到2.3.27版) 是 A(結(jié)束), 而 SUSv2 聲明是 C(結(jié)束且核心轉(zhuǎn)儲(chǔ)).)

下面 是 其他 幾個(gè) 信號(hào).

這里的 - 指 信號(hào) 不存在; 可能 給出 三個(gè)值, 第一個(gè)值 一般 用于 alpha 和 sparc, 中間的值 用于 i386, ppc 和 sh, 最后一個(gè) 是 mips 的. 信號(hào)29 在 alpha機(jī)上 是 SIGINFO / SIGPWR , 而在 sparc機(jī)上 是 SIGLOST

"動(dòng)作(Action)"欄 的 字母 有 下列 含義:

A

缺省動(dòng)作是結(jié)束進(jìn)程.

B

缺省動(dòng)作是忽略這個(gè)信號(hào).

C

缺省動(dòng)作是結(jié)束進(jìn)程, 并且核心轉(zhuǎn)儲(chǔ).

D

缺省動(dòng)作是停止進(jìn)程.

E

信號(hào)不能被捕獲.

F

信號(hào)不能被忽略.

(譯注: 這里 "結(jié)束" 指 進(jìn)程 終止 并 釋放資源, "停止" 指 進(jìn)程 停止 運(yùn)行, 但是 資源 沒(méi)有 釋放, 有可能 繼續(xù) 運(yùn)行.)

遵循 (CONFORMING TO)

POSIX.1

BUGS

SIGIO 和 SIGLOST 有 相同的 值. 后者 在 內(nèi)核 源碼 中 被注釋 掉了, 但是 某些 軟件 構(gòu)造的 進(jìn)程 仍然 認(rèn)為 信號(hào)29 是 SIGLOST.

另見(jiàn) (SEE ALSO)

kill(1), kill(2), setitimer(2)

#p#

NAME

signal - list of available signals  

DESCRIPTION

Linux supports both POSIX reliable signals (hereinafter "standard signals") and POSIX real-time signals.  

Standard Signals

Linux supports the standard signals listed below. Several signal numbers are architecture dependent, as indicated in the "Value" column. (Where three values are given, the first one is usually valid for alpha and sparc, the middle one for i386, ppc and sh, and the last one for mips. A - denotes that a signal is absent on the corresponding architecture.)

The entries in the "Action" column of the table specify the default action for the signal, as follows:

Term

Default action is to terminate the process.

Ign

Default action is to ignore the signal.

Core

Default action is to terminate the process and dump core.

Stop

Default action is to stop the process.

First the signals described in the original POSIX.1 standard.

The signals SIGKILL and SIGSTOP cannot be caught, blocked, or ignored.

Next the signals not in the POSIX.1 standard but described in SUSv2 and SUSv3 / POSIX 1003.1-2001.

Up to and including Linux 2.2, the default behaviour for SIGSYS, SIGXCPU, SIGXFSZ, and (on architectures other than SPARC and MIPS) SIGBUS was to terminate the process (without a core dump). (On some other Unices the default action for SIGXCPU and SIGXFSZ is to terminate the process without a core dump.) Linux 2.4 conforms to the POSIX 1003.1-2001 requirements for these signals, terminating the process with a core dump.

Next various other signals.

(Signal 29 is SIGINFO / SIGPWR on an alpha but SIGLOST on a sparc.)

SIGEMT is not specified in POSIX 1003.1-2001, but neverthless appears on most other Unices, where its default action is typically to terminate the process with a core dump.

SIGPWR (which is not specified in POSIX 1003.1-2001) is typically ignored by default on those other Unices where it appears.

SIGIO (which is not specified in POSIX 1003.1-2001) is ignored by default on several other Unices.  

Real-time Signals

Linux supports real-time signals as originally defined in the POSIX.4 real-time extensions (and now included in POSIX 1003.1-2001). Linux supports 32 real-time signals, numbered from 32 (SIGRTMIN) to 63 (SIGRTMAX). (Programs should always refer to real-time signals using notation SIGRTMIN+n, since the range of real-time signal numbers varies across Unices.)

Unlike standard signals, real-time signals have no predefined meanings: the entire set of real-time signals can be used for application-defined purposes. (Note, however, that the LinuxThreads implementation uses the first three real-time signals.)

The default action for an unhandled real-time signal is to terminate the receiving process.

Real-time signals are distinguished by the following:

1.

Multiple instances of real-time signals can be queued. By contrast, if multiple instances of a standard signal are delivered while that signal is currently blocked, then only one instance is queued.

2.

If the signal is sent using sigqueue(2), an accompanying value (either an integer or a pointer) can be sent with the signal. If the receiving process establishes a handler for this signal using the SA_SIGACTION flag to sigaction(2) then it can obtain this data via the si_value field of the siginfo_t structure passed as the second argument to the handler. Furthermore, the si_pid and si_uid fields of this structure can be used to obtain the PID and real user ID of the process sending the signal.

3.

Real-time signals are delivered in a guaranteed order. Multiple real-time signals of the same type are delivered in the order they were sent. If different real-time signals are sent to a process, they are delivered starting with the lowest-numbered signal. (I.e., low-numbered signals have highest priority.)

If both standard and real-time signals are pending for a process, POSIX leaves it unspecified which is delivered first. Linux, like many other implementations, gives priority to standard signals in this case.

According to POSIX, an implementation should permit at least _POSIX_SIGQUEUE_MAX (32) real-time signals to be queued to a process. However, rather than placing a per-process limit, Linux imposes a system-wide limit on the number of queued real-time signals for all processes. This limit can be viewed and (with privilege) changed via the /proc/sys/kernel/rtsig-max file. A related file, /proc/sys/kernel/rtsig-nr, can be used to find out how many real-time signals are currently queued.  

CONFORMING TO

POSIX.1  

BUGS

SIGIO and SIGLOST have the same value. The latter is commented out in the kernel source, but the build process of some software still thinks that signal 29 is SIGLOST.  

SEE ALSO

kill(1), kill(2), setitimer(2), sigaction(2), signal(2), sigprocmask(2), sigqueue(2)