Bug 14449
Summary: | Ambiguity in SIGSYS <-> SIGUNUSED portion of signal(7) | ||
---|---|---|---|
Product: | Documentation | Reporter: | Garrett Cooper (yaneurabeya) |
Component: | man-pages | Assignee: | documentation_man-pages (documentation_man-pages) |
Status: | RESOLVED CODE_FIX | ||
Severity: | low | CC: | alan, mtk.manpages |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.nabble.com/New-test-%3A-sniperkill---killing-processes-from-a-distance-td25986571.html | ||
Kernel Version: | 2.6.30-gentoo-r4 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
Application driven by the sniperkill script.
Execution log for kernel specified. Driver script for killme application |
Created attachment 23483 [details]
Execution log for kernel specified.
Created attachment 23484 [details]
Driver script for killme application
Thanks for this report. I applied the patch below. Satisfactory? --- a/man7/signal.7 +++ b/man7/signal.7 @@ -270,7 +270,7 @@ SIGBUS 10,7,10 Core Bus error (bad memory access) SIGPOLL Term Pollable event (Sys V). Synonym for \fBSIGIO\fP SIGPROF 27,27,29 Term Profiling timer expired -SIGSYS 12,\-,12 Core Bad argument to routine (SVr4) +SIGSYS 12,31,12 Core Bad argument to routine (SVr4) SIGTRAP 5 Core Trace/breakpoint trap SIGURG 16,23,21 Ign Urgent condition on socket (4.2BSD) SIGVTALRM 26,26,28 Term Virtual alarm clock (4.2BSD) @@ -304,7 +304,7 @@ SIGPWR 29,30,19 Term Power failure (System V) SIGINFO 29,\-,\- A synonym for \fBSIGPWR\fP SIGLOST \-,\-,\- Term File lock lost SIGWINCH 28,28,20 Ign Window resize signal (4.3BSD, Sun) -SIGUNUSED \-,31,\- Term Unused signal (will be \fBSIGSYS\fP) +SIGUNUSED \-,31,\- Core Synonymous with \fBSIGSYS\fP .TE (Signal 29 is @@ -328,6 +328,13 @@ by default on those other Unix systems where it appears. .B SIGIO (which is not specified in POSIX.1-2001) is ignored by default on several other Unix systems. + +Where defined, +.B SIGUNUSED +is synonymous with +.\" parisc is the only exception: SIGSYS is 12, SIGUNUSED is 31 +.B SIGSYS +on most architectures. .SS "Real-time Signals" Linux supports real-time signals as originally defined in the POSIX.1b real-time extensions (and now included in POSIX.1-2001). Sounds good -- thanks! |
Created attachment 23482 [details] Application driven by the sniperkill script. signal(7) states that signal # 31 for ppc, *86, etc should result in termination only, in the 3rd column, but the `will be SIGSYS' comment is unnecessarily ambiguous: SIGUNUSED -,31,- Term Unused signal (will be SIGSYS) SIGSYS 12,-,12 Core Bad argument to routine (SVID) The behavior as shown in my log for the `sniperkill' test I've recommended adding to LTP demonstrates that the behavior for SIGUNUSED matches SIGSYS. The documentation for SIGUNUSED should either clearly state a) that the process will `Core'-dump, and/or the indirection should be changed such that SIGUNUSED directly maps to SIGSYS. I've attached the logs and test. The email to ltp-list is in the URL field.