http://bugzilla.kernel.org/show_bug.cgi?id=14449 URL: http://www.nabble.com/New-test-%3A-sniperkill---killin g-processes-from-a-distance-td25986571.html Summary: Ambiguity in SIGSYS <-> SIGUNUSED portion of signal(7) Product: Documentation Version: unspecified Kernel Version: Linux orangebox 2.6.30-gentoo-r4 #1 SMP PREEMPT Sat Aug 8 19:31:26 PDT 2009 x86_64 Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz GenuineIntel GNU/Linux Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: low Priority: P1 Component: man-pages AssignedTo: documentation_man-pages@xxxxxxxxxxxxxxxxxxxx ReportedBy: yaneurabeya@xxxxxxxxx Regression: No Created an attachment (id=23482) --> (http://bugzilla.kernel.org/attachment.cgi?id=23482) 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. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
