Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<3BFA60AC.3080102@cportcorp.com>
Date:	Tue, 20 Nov 2001 08:54:52 -0500
From:	Peter Buckley <peter DOT buckley AT cportcorp DOT com>
User-Agent:	Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language:	en-us
MIME-Version:	1.0
To:	Shawn Behrens <sbehrens AT gmx DOT li>
CC:	cygwin AT cygwin DOT com
Subject:	Re: cygrunsrv sshd fails: Some clues
References:	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20011120080121 DOT 02440440 AT pop DOT gmx DOT li>

Have you tried starting the service as another user? When you install it 
as a service, typically the SYSTEM account runs it. Try giving a 
temporary account (or the account that can start it from the cmd line) 
the rights detailed in /usr/doc/cygwin/inetutils-x-x-x.README, and 
starting the service as that account to see if it works. The SYSTEM 
account is limited in subtle ways that can make troubleshooting difficult.

HTH,
Peter

Shawn Behrens wrote:

> Hello,
> 
> I saw in the archives that a guy with a Win2k machine had intermittent 
> failures of the sshd service (failure to start).
> 
> I get the exact same errors in my event log, just that it fails every 
> time. I'm running WinXP Pro.
> 
> Here's what I tried:
> 
> - Set the service to restart at first, second, and subsequent failures
>  -> Service does not start up. Only the initial error message is entered 
> into event log
>   Which could mean it is never restarted, or XP only logs the first 
> failure. Hmm. I shall set subsequent to 'start program' and see what 
> happens.
> 
> - Removed the enivronment key from parameters, as was suggested in a 
> post elsewhere (found through deja). No change.
> 
> 
> I can start sshd manually successfully every time. This leads me to 
> conclude that:
> 
> Since sshd is restarted every second on failure (if that is what happens):
> - The failure has nothing to do with dependencies
> - The failure has nothing to do with sshd being started early on in the 
> boot process
> 
> Since I can start it manually
> - The environment for a service being started manually must be different 
> from being started by the system, somehow
> 
> Hope this helps narrow it down!
> 
> Shawn
> 
> 
> -- 
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 


-- 
Your mouse has moved.
Windows NT must be restarted for the change to take effect.
Reboot now?  [OK]

--


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -