X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew DeFaria Subject: Re: Bash.exe stays open after Putty is closed Date: Sat, 05 Apr 2008 09:52:19 -0700 Lines: 13 Message-ID: References: <47F6B29F DOT 6020904 AT gmail DOT com> <20080405093513 DOT GT5532 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com NightStrike wrote: > Killing putty with Alt-F4 is the same as losing connectivity, or putty > crashing (rare as that is), or any of several other scenarios where > there is abnormal termination. Does bash remain running under any > abnormal termination? If so, that's a bug. If not, what makes things > like connectivity loss different from closing putty with Alt-f4? I agree, any cause of termination of the window should kill the children like bash. However, I'm curious, why are you using Putty instead of just ssh? I assume you mean Putty on Windows. If you have Cygwin why not simply do ssh ? -- Andrew DeFaria DUMBWAITER: one who asks if the kids would care to order dessert. -- 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/