Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <002201be5c36$a66ec820$02af6080@sokhapki-1.cc.bellcore.com>
From: "Sergey Okhapkin" <sos AT lab254 DOT bellcore DOT com>
To: "Curtis Galloway" <curtis AT pdi DOT com>, <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: Handling CTRL_LOGOFF_EVENT
Date: Fri, 19 Feb 1999 13:35:39 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOle: Produced By Microsoft MimeOLE V4.72.3110.3



>I submitted a fix a while ago to the winsup module regarding bash hanging
when
>I rebooted my NT machine.  The problem was that the cygwin signal handler
was
>returning TRUE after receiving a CTRL_CLOSE_EVENT or CTRL_SHUTDOWN_EVENT
window
>event, so Windows thought that cygwin programs refused to exit when you
were


It's very important to _ignore_ (return TRUE) CTRL_LOGOFF_EVENT to not
terminate cygwin apps running as services on user's logoff!

Sergey Okhapkin, http://www.lexa.ru/sos
Piscataway, NJ



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com