At 11:27 AM 12/11/2003, Matthew McGillis you wrote: >> > 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.
The "suggestion" is that SYSTEM has been proven to *NOT* be a sufficiently privileged user for W2K3 to run Cygwin services that require switching users. There's lot's of discussion of that in the email archives. You can skulk around yourself to see all the discussions. <http://cygwin.com/ml/cygwin/2003-09/msg00435.html> discusses the key issue. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/
