Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="US-ASCII"
Subject: bash: 3.2.25-17 Windows 2000 Runaway Bash process
Date: Fri, 18 Apr 2008 09:52:26 -0400
Message-ID: <0C3FC6B507AF684199E57BFCA3EAB553244BFE4C@NOANDC-MXU11.NOA.Alcoa.com>
From: "Sliva, Gregory C." <Gregory.Sliva@alcoa.com>
To: <cygwin@cygwin.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

Using SSH to connect to Windows 2000 server. After opening bash sessions
and closing out, bash.exe still remains on the Windows Task Manager as a
running process. After sometime, many bash.exe processes show as running
in the Task manager and eventually it restricts any more SSH connections
to this server. I am able to manually kill each bash process in the task
manager and eventually it will allow more SSH connections, but this
manual process is by no means the right approach. Has anyone experienced
this and how can you set it so that bash.exe is killed after an SSH
session is closed.

Thanks
Greg

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