I think that is it. I'll try an use Ralf's solution and make my stuff a real Service. It looks like Java folks have run into similar issues in the past: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4323062 This rather long page eventually explains the problem in fairly gory detail. Thanks, -- Jacob -----Original Message----- From: twisted-python-bounces@twistedmatrix.com [mailto:twisted-python-bounces@twistedmatrix.com] On Behalf Of Timothy Fitz Sent: Wednesday, September 27, 2006 6:35 AM To: Twisted general discussion; jacob@internet24.de Subject: Re: [Twisted-Python] Re: SIGBREAK on windows SIGBREAK will be sent if you have a program open in a console and close the window by clicking the x. This can happen to services if you're running them via a debug mechanism that connects them to the console. On 9/27/06, Thomas Jacob <jacob@internet24.de> wrote:
You may receive that signal when users log off. I'm using the following code to ignore signals when running as service (but I'm also using the win32serviceutil module to start as a service).
I've never got a sigbreak signal sent to my twisted/pywin32 services when users log off so far, under what circumstances or on which Windows platforms does this actually happen?
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python