| delorie.com/archives/browse.cgi | search |
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/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |