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: <3F1F7C41.5060007@t-online.de>
Date: Thu, 24 Jul 2003 08:27:13 +0200
From: =?ISO-8859-1?Q?Markus_Sch=F6nhaber?= <mks99 AT t-online DOT de>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: How to diagnose Cygwin / Windows shutdown problem
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0307232158590 DOT 26427-100000 AT slinky DOT cs DOT nyu DOT edu>
In-Reply-To: <Pine.GSO.4.44.0307232158590.26427-100000@slinky.cs.nyu.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Igor Pechtchanski wrote:
> There is such a mechanism on Win2k.  I don't think there is one on Win9x.
> This thread seems to indicate that there isn't one on WinXP, either, at
> least not for shutdown messages.
> 	Igor

I don't see any difference in the behaviour on W2k and WinXP. As Richard 
stated on the other thread, clicking the window's close button on WinXP 
does end bash (or python) - logging off doesn't. On W2k the behaviour is 
the same (just tried that too).

Regards
   mks

> 
> On Wed, 23 Jul 2003, Andrew DeFaria wrote:
> 
> 
>>Randall R Schulz wrote:
>>
>>
>>>Andrew,
>>>
>>>Cygwin apps don't have a Windows event handler do they?
>>
>>To tell you the truth... I don't know for sure.
>>
>>
>>>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).
>>
>>Makes sense to me! I would suspect that when one clicks on the close
>>button in the window frame that generates a Windows event that is
>>translated somehow to send a kill signal to the shell. If true then
>>there is already a mechanism for Win Event -> POSIX signal.
>>
>>
>>>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/