X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sat, 5 Apr 2008 14:00:12 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Bash.exe stays open after Putty is closed
Message-ID: <20080405180012.GC1244@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <47F6B29F DOT 6020904 AT gmail DOT com> <20080405093513 DOT GT5532 AT calimero DOT vinschen DOT de> <b609cb3b0804050639k7de6a062s102b098d9f7e55db AT mail DOT gmail DOT com> <ft8ao6$bjp$1 AT ger DOT gmane DOT org> <b609cb3b0804050958r553d468do215278855f7df5fa AT mail DOT gmail DOT com> <ft8bvu$fut$1 AT ger DOT gmane DOT org> <b609cb3b0804051037o390136adh411b2d6b6f48cfd5 AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b609cb3b0804051037o390136adh411b2d6b6f48cfd5@mail.gmail.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Sat, Apr 05, 2008 at 01:37:57PM -0400, NightStrike wrote:
>On 4/5/08, Andrew DeFaria <Andrew AT defaria DOT com> wrote:
>[snip lots of useless arguing]
>The takeaway is that if bash isn't handling a SIGHUP properly (As
>Paul-Kenji pointed out), then that is an issue that can't be ignored
>by saying "just use cygwin ssh".

Actually, maybe I missed something but the comment was "the process also
get a sighup I think".  That's hardly bug report or a definitive problem
statement.

I'd be very amazed if bash wasn't correctly dealing with SIGHUPs the
same way it does on linux.

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/