Lassi, I did follow this discussion, but this one is totally unrelated as the startup fails every time using cygrunsrv and works ok every time using invoker AND because sshd even never gets started.
Mit besten Grüssen, Kind regards, Patrick Hildenbrand > Patrick Hildenbrand > Operations & Technology > SAP Hosting AG & Co. KG > Raiffeisenring 45 > 68789 St. Leon-Rot, Germany > T +49/6227/7-66410 > F +49/6227/7-66301 > E [EMAIL PROTECTED] > http://www.saphosting.com -----Original Message----- From: Lassi A. Tuura [mailto:[EMAIL PROTECTED]] Sent: Dienstag, 12. Februar 2002 17:52 To: Hildenbrand, Patrick Cc: '[EMAIL PROTECTED]' Subject: Re: cygrunsrv does not start sshd in 1 out of 40 installs This could be due to service start-up delays. There was discussion on this in last October or thereabouts: exactly what other services sshd should depend on to start reliably. IIRC there were different solutions for different conditions and no universal solution; the failures were caused by TCP/IP or some related part had not properly started yet at the time sshd was attempting to start. Search the mail archive for more details. Look into your event logs to see if there are differences in the service startup order, especially on the failing machines. //lat -- Klein bottle for rent; enquire within. -- 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/
