X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: Date: Sat, 5 Apr 2008 12:58:14 -0400 From: NightStrike To: cygwin AT cygwin DOT com Subject: Re: Bash.exe stays open after Putty is closed In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47F6B29F DOT 6020904 AT gmail DOT com> <20080405093513 DOT GT5532 AT calimero DOT vinschen DOT de> 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 On 4/5/08, Andrew DeFaria wrote: > 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 ? I personally use putty because the putty console window is superb, and because it allows incredibly easy access to all of the many features of an ssh client. Plus, it supports both telnet and ssh, can handle a bazillion code pages / character sets (the most important being UTF-8), offers great logging support, per-connection profiles, complete control over hotkeys, easy handling of Backspace, one-click access to the alternate terminal screen buffer (for applications like vi), etc etc etc... If you have Windows, why NOT use putty? -- 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/