Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <5.2.1.1.2.20030723173105.038b9cb8@pop.sonic.net>
X-Sender: rschulz AT pop DOT sonic DOT net
Date: Wed, 23 Jul 2003 17:34:12 -0700
To: cygwin AT cygwin DOT com
From: Randall R Schulz <rschulz AT sonic DOT net>
Subject: Re: How to diagnose Cygwin / Windows shutdown problem
In-Reply-To: <bfn8fc$fu$1@main.gmane.org>
References: <5 DOT 2 DOT 1 DOT 1 DOT 2 DOT 20030723102245 DOT 03d4e2c8 AT pop DOT sonic DOT net>
 <003001c3513d$7caa3410$19c3fea9 AT RAnderson>
 <5 DOT 2 DOT 1 DOT 1 DOT 2 DOT 20030723102245 DOT 03d4e2c8 AT pop DOT sonic DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Andrew,

Cygwin apps don't have a Windows event handler do they? The two 
programming models (Win32 and POSIX) are fundamentally different, so 
based on my very limited understanding, it seems that Cygwin itself 
(code in Cygwin1.dll) would have to intercept these OS-generated events 
and translate them into POSIX signals (SIGUP, say).

Randall Schulz


At 17:16 2003-07-23, Andrew DeFaria wrote:
>Randall R Schulz wrote:
>
>>Cygwin apps don't know about and cannot respond to the 
>>system-generated messages that request that applications quit in 
>>preparation for the system to shut down or the user to log off.
>
>"Cannot respond to"? When a system-generated message that requests 
>that applications quit in preparation for the systme to shut down or 
>the user to log off why can Cygwin apps (in particular bash or other 
>shell) simply do what it would have done if TMOUT was just triggered?
>
>       TMOUT  If set to a value greater than zero, TMOUT  is  treated  as  the
>              default timeout for the read builtin.  The select command termi-
>              nates if input does not arrive after TMOUT seconds when input is
>              coming  from  a terminal.  In an interactive shell, the value is
>              interpreted as the number of seconds to  wait  for  input  after
>              issuing  the  primary prompt.  Bash terminates after waiting for
>              that number of seconds if input does not arrive.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/