Re: The implementation of SIGHUP in Win32 Perl

(Windows 7 terminates such processes after approximately 10 seconds). My understanding is that the OS terminates these processes upon the return from the handler,

Can you offer some evidence for either of these assertions?

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.

Comment on Re: The implementation of SIGHUP in Win32 Perl

Replies are listed 'Best First'.
Re^2: The implementation of SIGHUP in Win32 Perl by klaten (Novice) on Aug 31, 2013 at 17:35 UTC
This is becoming very interesting. This MSDN topic describes what I believe is the current behavior of the console control handlers. In this article, regarding the event handler returning "True" as it does in win32.c it says, "no other handler functions are called and the system terminates the process." I could find no definitive documentation of the "10 second" process timeout I described. However, this discussion on StackOverflow leads me to believe it is real. This behavior has changed over the years. This article provides a good description of how things worked at one point. Notice that there is no mention of threads at all. It seems that a change to the behavior of control handlers occurred beginning with Windows Vista (with Windows 7 apparently adding the previously mentioned 10 second timeout).	[reply]
Re^2: The implementation of SIGHUP in Win32 Perl by klaten (Novice) on Aug 30, 2013 at 20:39 UTC
BrowserUk, yes, there are some conversations over on StackOverflow and some MSDN notes, but I'll have to look up the links and post them later, sorry.	[reply]


good chemistry is complicated, and a little bit messy -LW
	PerlMonks