Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin@cygwin.com From: Andrew DeFaria Subject: Re: How to diagnose Cygwin / Windows shutdown problem Date: Wed, 23 Jul 2003 18:19:36 -0700 Lines: 54 Message-ID: References: <5.2.1.1.2.20030723102245.03d4e2c8@pop.sonic.net> <003001c3513d$7caa3410$19c3fea9@RAnderson> <5.2.1.1.2.20030723102245.03d4e2c8@pop.sonic.net> <5.2.1.1.2.20030723173105.038b9cb8@pop.sonic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en, zh In-Reply-To: <5.2.1.1.2.20030723173105.038b9cb8@pop.sonic.net> 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/