Mail Archives: cygwin/2001/11/20/08:12:13
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/
- Raw text -