This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: Handling CTRL_LOGOFF_EVENT
- To: "Curtis Galloway" <curtis@pdi.com>,<cygwin@sourceware.cygnus.com>
- Subject: Re: Handling CTRL_LOGOFF_EVENT
- From: "Sergey Okhapkin" <sos@lab254.bellcore.com>
- Date: Fri, 19 Feb 1999 13:35:39 -0500
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- Sender: cygwin-owner@sourceware.cygnus.com
>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@sourceware.cygnus.com