delorie.com/archives/browse.cgi | search |
Success! Thanks to a hint from Jason Tishler, I found that I overlooked one reference to "SHUTDOWN" in the Cygwin source code. (D'oh!) That code sends SIGHUP to itself in response to some window shutdown event. I don't think this shutdown event is the same as the SCM shutdown event, but in any case it kills the Cygwin process before the SCM-invoked handler gets a chance to run. I added code to my test service to catch, report, and otherwise ignore all signals. Then I started the service and left it running while I restarted my NT system (what a PITA test...). After reboot I see in the log file that SIGHUP was received. And now the service control handler also runs, getting the SHUTDOWN event and leading to clean process shutdown. Finally. Thanks for the help, all who responded. -- Fred Yankowski fred AT OntoSys DOT com tel: +1.630.879.1312 Principal Consultant www.OntoSys.com fax: +1.630.879.1370 OntoSys, Inc 38W242 Deerpath Rd, Batavia, IL 60510, USA -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |