bash: 3.2.25-17 Windows 2000 Runaway Bash process

bash: 3.2.25-17 Windows 2000 Runaway Bash process

[Sliva, Gregory C.]

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/

Re: bash: 3.2.25-17 Windows 2000 Runaway Bash process

[Larry Hall (Cygwin)]

Sliva, Gregory C. wrote:
> Using SSH to connect to Windows 2000 server. After opening bash sessions
> and closing out...

Don't click on the "x" to close the window.  Exit with "exit" or "logout".


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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