Raphael Geissert <[EMAIL PROTECTED]> writes: > Russ Allbery wrote: > >> Clint Adams <[EMAIL PROTECTED]> writes: >> >>> Since 0.5.6, it does not; the only number it understands is the >>> pseudo-signal 0, mandated by POSIX. >> >> Oh, sorry, you're of course correct. I missed the 0 == n test in >> gettrap(). Sorry about the confusion. >> >>> The reason POSIX doesn't allow numbers is that they are inconsistent >>> from platform to platform. People who learn signals on a commercial OS >>> of yore sometimes assume that signal 5 means something other than >>> SIGTRAP on Debian, and script traps and kills that end up not doing what >>> is intended. >> >> This is a good point. However, it's worth noting that the XSI extension >> to POSIX doesn't allow you to use just any numbers. It specifically lets >> you use numbers for HUP, INT, QUIT, ABRT, KILL, ALRM, and TERM and nothing >> else. I think that's fairly portable. >> > > So should I only ignore those specifying a signal number in the 1-15 range?
I'd suggest complaining about those that specify numbers other than 0, 1, 2, 3, 6, 9, 14, or 15. See http://www.opengroup.org/onlinepubs/009695399/utilities/trap.html -- Ben Pfaff http://benpfaff.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
