Clear questions and runnable code get the best and fastest answer |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
In theory, the process is only terminated if do_raise() returns true; that only happens if there is no signal handler set for sighup. If there is a signal handler set, it gets called by do_raise(), whence it has as long as it decides to take, and sig_terminate() is never called. There is no sense in adding a Sleep 950; (which is a little under a second not 9.5 seconds) anywhere. In reality, I can't get a sighup signal handler to ever be invoked even on 5.18. I run vista, and I never see a dialog prompting me; nor is there any delay 10s or otherwise between killing the process and it disappearing; regardless of whether I've installed a signal handler for HUP. I'm not really sure I understand your motivation for meditating on this; but I think you need to do a lot more reading and experimenting. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
In reply to Re: The implementation of SIGHUP in Win32 Perl
by BrowserUk
|
|