X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
X-SpamScore: 1
X-Spam-Summary: 2,0,0,5921a51307cdff85,3ec6fd5b748b7490,michael AT hipp DOT com,cygwin AT cygwin DOT com,RULES_HIT:152:355:379:599:601:854:945:946: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:2379:2393:2559:2562:2692:2904:3027:3353:3865:3866:3867:3868:3869:3870:3871:3872:3873:3874:3876:3877:4250:4362:4470:5007:6114:6117:6119:6120:7652:7901:7903:7974:8501:8660,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: <4929A1D6.9080001@Hipp.com>
Date: Sun, 23 Nov 2008 12:32:54 -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> <492980CF DOT 9000408 AT Hipp DOT com> <ggc1mk$ffo$2 AT ger DOT gmane DOT org>
In-Reply-To: <ggc1mk$ffo$2@ger.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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:
> That's the Windows/Cygwin emulation of a Unix fork. Should be the same 
> as on Linux.

I know that. I was pointing out that sshd goes away as expected but bash does not.

> Please read again what I wrote and try to understand it.

Ok, I have re-read it and don't find anything that I failed to understand. 
Even on the 2nd or 3rd readings.

> In all 
> likelihood you do NOT want sshd to kill your shell because you loose 
> connection for a while. Let me repeat: you do NOT want that.

Really? Should I call Red Hat, SUSE, Debian and Ubuntu and all the others and 
tell them they've been doing it wrong all these years? That's *exactly* how 
every Linux I've ever used works.

> You want 
> the ability to reconnect to that session once the physical connection is 
> reestablished. "screen" gives you that ability.

I know about "screen". I use it regularly. But screen is off-topic. Unless 
there is some way screen can re-connect to a dangling bash session; I thought 
screen could only re-connect to screen. If it has that ability I'd like to be 
educated to it.

Some days ago I brought up a GUI session to a remote W2k3 box, ran task 
manager and almost fell out of my chair to see bash.exe listed nearly a dozen 
times. I thought the thing had been rooted or something.

Surely there is some actual solution to this. It works splendidly on Linux. 
And when I am doing something critical that doesn't need to be interrupted, 
then our mutual friend "screen" is always there waiting.

Can anyone offer some help? Please?

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/