>>>>> "RN" == Ranga Nathan <[EMAIL PROTECTED]> writes:
RN> I just read the signals section of Programming Perl 2nd edition RN> (my precious book with Larry Walls autograph, camel stamp and RN> TMTOWTDI stamp) which cautions against doing anything worthwhile RN> after handling a signal, since the underlying C routines are not RN> re-entrant on most platforms. In my case there is only one RN> instance of the script required to run at any time (ha ha, soon RN> there will pop up an exception!) , so it is OK. in perl 5.8 signals are safe (they have a delayed delivery between perl ops) so that doesn't matter. or you could use a c based event loop like Event.pm that handles signals cleanly. RN> The book also states that you can not IGNORE or trap a A KILL or STOP RN> signal. Is it still the case with Perl 5.8 and Linux kernel 2.4x? that is an OS issue and not a perl one. perl can't do any more than the OS allows and those signals can't be caught because they are designed that way. kill means kill so why allow it to be caught? and stop is what a parent (debugger maybe?) sends to a child to manage it so again, the child will never want to catch it. uri -- Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com --Perl Consulting, Stem Development, Systems Architecture, Design and Coding- Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org _______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
