Re: How to diagnose Cygwin / Windows shutdown problem
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/
Re: How to diagnose Cygwin / Windows shutdown problem
I don't know for sure either, but by the end of a day, it is not unusual for me to see multiple instances of bash.exe within my task manager, despite having closed them in windows. Therefore I don't think there is windows-posix signal translation, just the other way around. 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 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/
Re: How to diagnose Cygwin / Windows shutdown problem
do any of the cygwin Libraries have a signal function? If so does the cygwin singal function handle the signal values SIGABRT Abnormal termination SIGFPE Floating-point error SIGILL Illegal instruction SIGINT CTRL+C signal SIGSEGV Illegal storage access SIGTERM Termination request Besides opening and closing the windows I sincerely doubt cygwin is sending or receiving any window events.. Something to think about.. -Martin - Original Message - From: David Sharp [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 24, 2003 5:41 AM Subject: Re: How to diagnose Cygwin / Windows shutdown problem I don't know for sure either, but by the end of a day, it is not unusual for me to see multiple instances of bash.exe within my task manager, despite having closed them in windows. Therefore I don't think there is windows-posix signal translation, just the other way around. 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 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/ -- 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/
Re: How to diagnose cygwin / Windows shutdown problem
On Thu, Jul 24, 2003 at 09:12:55AM -0700, Martin Gainty wrote: do any of the cygwin Libraries have a signal function? Huh? 1) You can check this for yourself. 2) What kind of UNIX emulation would cygwin be if it didn't have signal handling? Besides opening and closing the windows I sincerely doubt cygwin is sending or receiving any window events.. Yeah. If only there was *some way* to know for sure rather than send lots of speculation to a mailing list. It sure is a mystery. -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to [EMAIL PROTECTED] and be permanently blocked from mailing lists at sources.redhat.com -- 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/
RE: How to diagnose cygwin / Windows shutdown problem
So, does bash install the console control handler? If it does it probably can handle shotdown events. -Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED] Sent: Thu, July 24, 2003 5:22 PM To: [EMAIL PROTECTED] Subject: Re: How to diagnose cygwin / Windows shutdown problem On Thu, Jul 24, 2003 at 09:12:55AM -0700, Martin Gainty wrote: do any of the cygwin Libraries have a signal function? Huh? 1) You can check this for yourself. 2) What kind of UNIX emulation would cygwin be if it didn't have signal handling? Besides opening and closing the windows I sincerely doubt cygwin is sending or receiving any window events.. Yeah. If only there was *some way* to know for sure rather than send lots of speculation to a mailing list. It sure is a mystery. -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to [EMAIL PROTECTED] and be permanently blocked from mailing lists at sources.redhat.com -- 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/ -- 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/
Re: How to diagnose Cygwin / Windows shutdown problem
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. Are you saying that when you click close on a shell window and Windows sends an event (WM_CLOSE I think) Cygwin does catch this but when you do shutdown of Windows then Windows does not send some event to all processes informing them to shutdown? Or are you saying that when you do shutdown of Windows then Windows does send some event to all processes informing them to shutdown but Cygwin for some reason cannot catch this one? Why would Cygwin be able to catch the WM_CLOSE but not the WM_SHUTDOWN? -- 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/
Re: How to diagnose Cygwin / Windows shutdown problem
David Sharp wrote: I don't know for sure either, but by the end of a day, it is not unusual for me to see multiple instances of bash.exe within my task manager, despite having closed them in windows. Therefore I don't think there is windows-posix signal translation, just the other way around. There is a known issue that if you use rxvt and close it by using the close button then the underlying bash shell hangs around. If you use a Windows console window and run the shell in it and then close the window using the close button then the bash shell is properly notified to terminate and does so. If you are careful and always exit your shells with exit and never use the close button for rxvt windowed shells you shouldn't get shell processes hanging around. -- 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/
How to diagnose Cygwin / Windows shutdown problem
When I start Cygwin 1.3.22-1 and then try to shut down Windows XP using the normal Start / Turn Off Computer procedure, Windows pops up the End Program - Cygwin ... Windows cannot end this program dialog box. The cygwin ps command shows only a bash shell running. I tried using Start / Run / msconfig to disable the startup of all applications and rebooting, but the problem persists. I'm guessing that the next step would be to uninstall and reinstall Cygwin. Any suggestions? Richard Anderson [EMAIL PROTECTED] [EMAIL PROTECTED] www.richard-anderson.org www.raycosoft.com - Original Message - From: Richard Anderson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 21, 2003 9:00 PM Subject: Cygwin prevents normal Windows shutdown When I start Cygwin 1.3.22-1 with the installed shortcut (which points to C:\cygwin\cygwin.bat) and then try to shut down Windows XP using the normal Start / Turn Off Computer procedure, Windows pops up the End Program - Cygwin ... Windows cannot end this program dialog box. The cygwin ps command shows only a bash shell running. Is there some way to prevent this behavior? Richard Anderson [EMAIL PROTECTED] [EMAIL PROTECTED] www.richard-anderson.org www.raycosoft.com -- 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/
Re: How to diagnose Cygwin / Windows shutdown problem
I'm happy to end bash with an exit or ctrl-D to allow it to keep its records in order. When Windows cannot end... you have the choice of killing it or winding it up properly. -Original Message- From: Richard Anderson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Wed, 23 Jul 2003 10:02:01 -0700 Subject: How to diagnose Cygwin / Windows shutdown problem When I start Cygwin 1.3.22-1 and then try to shut down Windows XP using the normal Start / Turn Off Computer procedure, Windows pops up the End Program - Cygwin ... Windows cannot end this program dialog box. The cygwin ps command shows only a bash shell running. I tried using Start / Run / msconfig to disable the startup of all applications and rebooting, but the problem persists. I'm guessing that the next step would be to uninstall and reinstall Cygwin. Any suggestions? Richard Anderson [EMAIL PROTECTED] [EMAIL PROTECTED] www.richard-anderson.org www.raycosoft.com - Original Message - From: Richard Anderson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 21, 2003 9:00 PM Subject: Cygwin prevents normal Windows shutdown When I start Cygwin 1.3.22-1 with the installed shortcut (which points to C:\cygwin\cygwin.bat) and then try to shut down Windows XP using the normal Start / Turn Off Computer procedure, Windows pops up the End Program - Cygwin ... Windows cannot end this program dialog box. The cygwin ps command shows only a bash shell running. Is there some way to prevent this behavior? Richard Anderson [EMAIL PROTECTED] [EMAIL PROTECTED] www.richard-anderson.org www.raycosoft.com -- 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/ Tim Prince -- 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/
Re: How to diagnose Cygwin / Windows shutdown problem
Richard, You know, we heard you the first time... At 10:02 2003-07-23, Richard Anderson wrote: When I start Cygwin 1.3.22-1 and then try to shut down Windows XP using the normal Start / Turn Off Computer procedure, Windows pops up the End Program - Cygwin ... Windows cannot end this program dialog box. The cygwin ps command shows only a bash shell running. I tried using Start / Run / msconfig to disable the startup of all applications and rebooting, but the problem persists. I'm guessing that the next step would be to uninstall and reinstall Cygwin. Any suggestions? Where do people get this from? Maybe you should buy a brand new PC and start by formatting the drives, installing the OS, other applications and Cygwin. 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. You just have to manually quit running Cygwin applications before shutting down Windows. If you prefer one-stop shopping, you can initiate shutdown from within Cygwin. If that works for you, do something like this: # Quit all Cygwin applications % shutdown -r now; exit There's no man page or info entry for shutdown, so you if you want information on its operation, use shutdown --help: % shutdown --help Usage: shutdown [OPTION]... time Bring the system down. -f, --force Forces the execution. -s, --shutdown The system will shutdown and power off (if supported) -r, --reboot The system will reboot. -h, --hibernate The system will suspend to disk (if supported) -p, --suspendThe system will suspend to RAM (if supported) --help Display this help and exit. --versionOutput version information and exit. `time' is either the time in seconds or `+' and the time in minutes or a timestamp in the format `hh:mm' or the word now for an immediate action. To reboot is the default if started as `reboot', to hibernate if started as `hibernate', to suspend if started as `suspend', to shutdown otherwise. Good luck. Randall Schulz Richard Anderson -- 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/
Re: How to diagnose Cygwin / Windows shutdown problem
So this is a know issue? Seems like non-standard behavior for a Windows app. All Windows apps that I know of catch the shutdown interrupt, clean up their data structures and exit gracefully. Is there some reason why Cygwin can't do this? Richard Anderson [EMAIL PROTECTED] [EMAIL PROTECTED] www.richard-anderson.org www.raycosoft.com - Original Message - From: Timothy C Prince [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 10:27 AM Subject: Re: How to diagnose Cygwin / Windows shutdown problem I'm happy to end bash with an exit or ctrl-D to allow it to keep its records in order. When Windows cannot end... you have the choice of killing it or winding it up properly. -Original Message- From: Richard Anderson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Wed, 23 Jul 2003 10:02:01 -0700 Subject: How to diagnose Cygwin / Windows shutdown problem When I start Cygwin 1.3.22-1 and then try to shut down Windows XP using the normal Start / Turn Off Computer procedure, Windows pops up the End Program - Cygwin ... Windows cannot end this program dialog box. The cygwin ps command shows only a bash shell running. I tried using Start / Run / msconfig to disable the startup of all applications and rebooting, but the problem persists. I'm guessing that the next step would be to uninstall and reinstall Cygwin. Any suggestions? Richard Anderson [EMAIL PROTECTED] [EMAIL PROTECTED] www.richard-anderson.org www.raycosoft.com - Original Message - From: Richard Anderson [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 21, 2003 9:00 PM Subject: Cygwin prevents normal Windows shutdown When I start Cygwin 1.3.22-1 with the installed shortcut (which points to C:\cygwin\cygwin.bat) and then try to shut down Windows XP using the normal Start / Turn Off Computer procedure, Windows pops up the End Program - Cygwin ... Windows cannot end this program dialog box. The cygwin ps command shows only a bash shell running. Is there some way to prevent this behavior? Richard Anderson [EMAIL PROTECTED] [EMAIL PROTECTED] www.richard-anderson.org www.raycosoft.com -- 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/ Tim Prince -- 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/
Re: How to diagnose Cygwin / Windows shutdown problem
Richard Anderson wrote: So this is a know issue? Seems like non-standard behavior for a Windows app. All Windows apps that I know of catch the shutdown interrupt, clean up their data structures and exit gracefully. Is there some reason why Cygwin can't do this? Let's turn the question around. Are you interested in implementing and submitting a patch to do this? I'm sure folks here would be willing to discuss the viability of such functionality in the context of a patch to implement it. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/
Re: How to diagnose Cygwin / Windows shutdown problem
- Original Message - From: Larry Hall [EMAIL PROTECTED] To: Richard Anderson [EMAIL PROTECTED] Cc: Timothy C Prince [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 11:41 AM Subject: Re: How to diagnose Cygwin / Windows shutdown problem Richard Anderson wrote: So this is a know issue? Seems like non-standard behavior for a Windows app. All Windows apps that I know of catch the shutdown interrupt, clean up their data structures and exit gracefully. Is there some reason why Cygwin can't do this? Let's turn the question around. Are you interested in implementing and submitting a patch to do this? I'm sure folks here would be willing to discuss the viability of such functionality in the context of a patch to implement it. Timothy, your response might be interpreted as an attempt to discourage the user community from reporting problems or questioning apparent design flaws. I would think that a discussion group like this is the proper forum for submitting comments like my original e-mail. Any open-source software project that doesn't encourage comments from the user community is cutting itself off from a valuable source of feedback. Richard Anderson [EMAIL PROTECTED] [EMAIL PROTECTED] www.richard-anderson.org www.raycosoft.com -- 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/
Re: How to diagnose Cygwin / Windows shutdown problem
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/
Re: How to diagnose Cygwin / Windows shutdown problem
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/
Re: How to diagnose cygwin / Windows shutdown problem
On Wed, Jul 23, 2003 at 05:34:12PM -0700, Randall R Schulz wrote: Cygwin apps don't have a Windows event handler do they? They do in some situations but not by default. cgf -- 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/
Re: How to diagnose Cygwin / Windows shutdown problem
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/
Re: How to diagnose Cygwin / Windows shutdown problem
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 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. -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- 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/
