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 Date: Tue, 5 Aug 2003 18:07:43 +0300 From: Ville Herva To: cygwin AT cygwin DOT com Subject: Re: Administrator lacking super-user privileges on cygwin installation Message-ID: <20030805150743.GB221723@niksula.cs.hut.fi> References: <20030805055624 DOT GA221723 AT niksula DOT cs DOT hut DOT fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i On Tue, Aug 05, 2003 at 08:07:43AM -0400, you [Igor Pechtchanski] wrote: > > IIRC, the default installation of sshd as service used the event log for > all output, rather than /var/log/sshd.log (though I'm not too sure on this > one)... It certainly seems to, in the event log, there are sshd generated entries. > However, error code 255 means that the executable could not be executed. Ack. > Check the permissions on sshd ("ls -l /usr/sbin/sshd") $ ls -l /usr/sbin/sshd -rwxrwxrwx 1 Administ mkgroup_ 286720 May 22 23:44 /usr/sbin/sshd That should be runnable by SYSTEM, right? > and the mounts ("/", at least, should be a system mount). $ mount c:\cygwin\bin on /usr/bin type system (binmode) c:\cygwin\lib on /usr/lib type system (binmode) c:\cygwin on / type system (binmode) $ echo $CYGWIN binmode ntsec tty -- v -- v AT iki DOT fi -- 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/