On Thu, Mar 13, 2003 at 01:33:44PM +0100, Rafael Garcia-Suarez wrote: > "H.Merijn Brand" <[EMAIL PROTECTED]> wrote: > > -1 not allowed? > > Dunno, I was thinking that signal numbers must be (logically) > positive numbers.
Not true. Can have zero, too. > So I introduced this test in Config.t (change 18891) to help tracking > a problem on Linux/Gentoo. > But now I see that : > > $ uname -a > HP-UX galhp B.10.20 E 9000/806 1966347252 8-user license > $ grep RTMIN /usr/include/sys/signal.h > #define SIGRTMIN (-1) /* P1003.4/D14.1 3.3.1.1 */ Yeah. Note this really doesn't mean that to send SIGRTMIN one sends a minus one, in fact SIGRTMIN in itself is not a real signal (the symbol, that is, the value might be...) SIGRTMIN and SIGRTMAX (inclusive) are first of all defined to be runtime, not compiletime. (That many systems define it as compiletime is true, but they are still runtime in nature.) SIGRTMIN...SIGRTMAX (inclusive) denote the range of signals reserved for realtime signals. I am not certain but I suspect/guess that SIGRTMIN == -1 means there are no realtime signals at all. I think my patch suggestion to Configure where less-than-zero signals are just simply not detected should be a reasonable workaround. Perl doesn't do the POSIX realtime signals anyway. > Duh. There are actually OSes out there with negative signal numbers. -- Jarkko Hietaniemi <[EMAIL PROTECTED]> http://www.iki.fi/jhi/ "There is this special biologist word we use for 'stable'. It is 'dead'." -- Jack Cohen
