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 Message-ID: <4231EC9E.9040604@real.com> Date: Fri, 11 Mar 2005 11:08:14 -0800 From: Jeff Silverman User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040301 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Problems starting SSHD References: <4231D448 DOT 7090208 AT real DOT com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Igor Pechtchanski wrote: >On Fri, 11 Mar 2005, Igor Pechtchanski wrote: > > > >>On Fri, 11 Mar 2005, Jeff Silverman wrote: >> >> >> >>>sshd : PID 1696 : starting service `sshd' failed: execv: 1, Operation >>>not permitted. >>> >>> >Here's the "real" incantation: > >cygcheck /usr/sbin/sshd.exe | sed -ne 's,\\,/,g' -e '/cygwin/p' | \ > xargs cygpath -u | xargs chmod a+x > >Sorry for letting that test bit through... > > >>(as is, on 2 lines -- just cut-and-paste to your shell). >> >>Also, "chmod a+x /bin". >> >> >> >>>and >>> >>>sshd : PID 2548 : starting service `' failed: redirect_fd: open (1, >>>/var/log/sshd.log): 13, Permission denied. >>> >>> >>Try "chmod a+x /var /var/log" and >>"chown SYSTEM.SYSTEM /var/log/sshd.log && chmod 644 /var/log/sshd.log" >> >> >> >>>I have attached the output of cygcheck -svr as the file >>>cygcheck)output.txt. >>>What else should I look at, please? >>> >>> >>It's always a good idea to check permissions on anything that might be >>used in a program running as service, just to make sure that the SYSTEM >>user (which is used to run services, a.k.a. LocalSystem) has appropriate >>access. >> >>HTH, >> Igor >> >> > > > I tried the incantation (You're a clever script coder) and the chmod commands but to no avail. Insofar as I can tell, system has access to all of the files it is looking for. I even tried chmod 777 /var/log/sshd.log in an effort to identify the problem.. I also went through a cygwin installation on a Windows/2000 machine using the same procedure as the Windows/2003 server machine, and it works just fine. So I conclude that there is some subtle difference between W2K3 and W2K which is tripping up Cygwin for some reason. Maybe that's naive. Thank you in advance for your assistance. Jeff -- 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/