X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Thorsten Kampe <thorsten AT thorstenkampe DOT de>
Subject:	Re: Bash process hangs around forever after ssh disconnect
Date:	Sun, 23 Nov 2008 16:31:39 +0100
Lines:	15
Message-ID:	<ggbt21$84g$1@ger.gmane.org>
References:	<4928624D DOT 8090800 AT Hipp DOT com>
Mime-Version:	1.0
User-Agent:	MicroPlanet-Gravity/2.70.2067
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

* Michael Hipp (Sat, 22 Nov 2008 13:49:33 -0600)
> I'm logging in to a W2k server via cygwin sshd and using Putty as my
> terminal emulator. If my ssh connection gets dropped for any reason
> the bash.exe process on the host just stays there forever. Also,
> anything I was running in bash (e.g. vim) will stay there forever. I'm
> having to use taskman to clean this up periodically.
> 
> Anything that can be done about this?

You could check or set you the ClientAliveInterval and TCPKeepAlive. 
I've set both to 0 respectively to no because I don't want sshd to kill 
my session only because the client does not respond for a while. Use 
"screen" to reconnect when the connection is back.

Thorsten


--
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/

- Raw text -