Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Mime-Version:	1.0
X-Sender:	matthew AT mail DOT jenika DOT com
Message-Id:	<a06002002bbfd69e06bbb@[65.102.135.163]>
Date:	Wed, 10 Dec 2003 16:38:56 -0800
To:	cygwin AT cygwin DOT com
From:	Matthew McGillis <matthew AT mcgillis DOT org>
Subject:	shell under sshd fail to fork child process
X-Scanned-By:	MIMEDefang 2.37

I have installed the latest and greatest cygwin and sshd on a Small 
Business Windows Server 2003. Everything works great on the console 
and ssh'ing in and out works fine. However once I access the web 
server running on the box anyone sshd in will no longer be able to 
run anything that creates a child process. All cygwin functionality 
from the console still works fine. I can look at the processes and 
see srvc sshd and shells all running under SYSTEM. Once it gets into 
this state no additional connections to sshd can be made. The service 
can be stopped but starting it back up will not allow it to accept 
connections.

The only thing I have found that will get the sshd to respond again 
is to shut the server down and restart at which time it will again 
work great until someone accesses the web server.

If anyone is interested in this problem and would like additional 
information I'm happy to try what ever would help someone to look at 
it closer.

Thanks,
Matthew

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

- Raw text -