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 Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3C694843.A44BEAA@cern.ch> Date: Tue, 12 Feb 2002 17:52:19 +0100 From: "Lassi A. Tuura" Organization: Northeastern University, Boston, USA X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Hildenbrand, Patrick" CC: "'cygwin AT cygwin DOT com'" Subject: Re: cygrunsrv does not start sshd in 1 out of 40 installs References: <1275A224C449D4119CE900508B6FF0B302D32CEE AT dewdfx20> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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/