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: Thu, 24 Jul 2003 12:34:34 -0700 Lines: 16 Message-ID: References: <3F1FD3E4.5030804@btopenworld.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; 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: <3F1FD3E4.5030804@btopenworld.com> 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/