Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: In-Reply-To: References: Date: Thu, 11 Dec 2003 08:27:55 -0800 To: Brian Ford From: Matthew McGillis Subject: Re: shell under sshd fail to fork child process Cc: cygwin AT cygwin DOT com Content-Type: text/plain; charset="us-ascii" ; format="flowed" 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. >> >Oops! ^ Not sure what your suggesting with this but for clarification I should point out that the bash child shells of sshd are not running as SYSTEM but as who ever logged in. My main point with that is that from the console it is still easy to see that things look fairly normal even though those shells tied to sshd can not fork processes. -- 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/