X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: Date: Sat, 5 Apr 2008 09:39:09 -0400 From: NightStrike To: cygwin AT cygwin DOT com Subject: Re: Bash.exe stays open after Putty is closed In-Reply-To: <20080405093513.GT5532@calimero.vinschen.de> 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, Corinna Vinschen wrote: > On Apr 4 18:58, Christian Borchert wrote: > > I just installed Cygwin with OpenSSH and got it setup on Windows Server > > 2003. > > When I use Putty on a remote machine to connect to the server, the server > > starts a bash.exe processes. > > When I close Putty (alt-f4) the bash.exe processes remains on the server. > > Don't do that. Leave bash with Ctrl-D or exit. 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? -- 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/