X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<89fae3950804290756y44a68734ga4744750e65b41a4@mail.gmail.com>
Date:	Tue, 29 Apr 2008 10:56:02 -0400
From:	"=?UTF-8?Q?Fran=C3=A7ois_Rousseau?=" <francois DOT rousseau DOT tech AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	openssh, bash.exe, windows 2003, bash stay open
MIME-Version:	1.0
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
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id m3TEuetl028390

Hi,
I'm using Openssh under Cygwin on many Windows 2003 servers.
The problem:  my users kill the ssh connection (putty and ssh) insteadof using the "exit" command so the bash.exe attached with session stayopen and eventually this cause a problem ( sshd: PID 1944: error:session_pty_req: session 0 alloc failed.)
It's seems strange to me that the bash.exe stay open.  Do you have anyidea how to solve this issue?
The really old port of openssh for windows"http://sshwindows.sourceforge.net/" don't have this problem.
Thanks,François

- Raw text -