X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
X-SpamScore:	1
X-Spam-Summary:	2,0,0,dfebc7434a51a3f5,3ec6fd5b748b7490,michael AT hipp DOT com,cygwin AT cygwin DOT com,RULES_HIT:152:355:379:599:601:854:988:989:1187:1260:1261:1277:1311:1313:1314:1345:1358:1359:1437:1515:1516:1518:1534:1541:1593:1594:1676:1711:1730:1747:1766:1792:2393:2553:2559:2562:2693:2900:3027:3353:3865:3866:3867:3868:3869:3870:3871:3872:3873:3874:3876:3877:4362:5007:6114:6117:6119:6120:7652:7875:7901:7903:8501:8957,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:none,DNSBL:none
Message-ID:	<492980CF.9000408@Hipp.com>
Date:	Sun, 23 Nov 2008 10:11:59 -0600
From:	Michael Hipp <Michael AT Hipp DOT com>
Reply-To:	Michael AT Hipp DOT com
User-Agent:	Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Bash process hangs around forever after ssh disconnect
References:	<4928624D DOT 8090800 AT Hipp DOT com> <ggbt21$84g$1 AT ger DOT gmane DOT org>
In-Reply-To:	<ggbt21$84g$1@ger.gmane.org>
X-session-marker:	4D69636861656C40486970702E636F6D
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

Thorsten Kampe wrote:
> * 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.

Thanks. I set these options as per the man page and after restarting the sshd 
service it has had no effect on the problem. Appears it may be more related to 
bash than sshd per this...

  - When the system is idle I have one (1) sshd.exe process (the service).

  - Once I log in remotely I have two (2) sshd.exe processes and one (1) 
bash.exe process.

  - When I force exit the client terminal emulator one of the sshd.exe 
processes goes away almost immediately. But the one bash.exe process is still 
there (even as much as hours or days later).

Appears there's some lack of understanding between sshd and bash.

Any ideas?

Thanks,
Michael

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