Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Mime-Version: 1.0
X-Sender: matthew@mail.jenika.com
Message-Id: <a06002003bbfd706ff572@[65.102.135.163]>
In-Reply-To: <Pine.GSO.4.58.0312101844520.28297@eos>
References: <a06002002bbfd69e06bbb@[65.102.135.163]>
 <Pine.GSO.4.58.0312101844520.28297@eos>
Date: Thu, 11 Dec 2003 08:27:55 -0800
To: Brian Ford <ford@vss.fsi.com>
From: Matthew McGillis <matthew@mcgillis.org>
Subject: Re: shell under sshd fail to fork child process
Cc: cygwin@cygwin.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/

