X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 	tests=AWL,BAYES_00,SARE_SUB_FOREVER,SPF_PASS
X-Spam-Check-By: sourceware.org
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: 1.5.25-15: bash.exe hangs forever
Date: Wed, 2 Sep 2009 11:19:04 -0400
Message-ID: <CC93624851A47D42AFD22FB06BCD2D9A0245DD6A@CORPUSMX80B.corp.emc.com>
In-Reply-To: <b221b14e0909020816h20bcf035w548c39c0cab57748@mail.gmail.com>
References: <b221b14e0909020738m18702da0x490d940a3b4a75cf AT mail DOT gmail DOT com> <b221b14e0909020816h20bcf035w548c39c0cab57748 AT mail DOT gmail DOT com>
From: <Dexter_Michael AT emc DOT com>
To: <littlesuns AT gmail DOT com>, <cygwin AT cygwin DOT com>
X-EMM-EM: Active
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

Have you tried typing exit first?

Alt+F4 seems aggressive to me.  I know it works but I have always been taug=
ht to exit my shells.

-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of=
 Reed Wang
Sent: Wednesday, September 02, 2009 11:16 AM
To: cygwin AT cygwin DOT com
Subject: 1.5.25-15: bash.exe hangs forever

Hi All,
Sorry for no cygcheck report, there are some reason.

I build a SSH Server on Windows 2003 with Cygwin and when I close my
client with Alt+F4,=A0 on the server bash.exe process still hangs there,
it must be stopped manually, it seems there is a similar question
before <http://www.nabble.com/Bash-process-hangs-around-forever-after-ssh-d=
isconnect-td20639873.html>
but haven't been=A0 resolved, just want to know is there any solution
that when sshd stopped all the child process will be killed, so that
no need to do some job by hand.



Thank you

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple