Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <1275A224C449D4119CE900508B6FF0B302D32CF2@dewdfx20>
From: "Hildenbrand, Patrick" <patrick DOT hildenbrand AT sap DOT com>
To: "'Lassi A. Tuura'" <lassi DOT tuura AT cern DOT ch>
Cc: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: RE: cygrunsrv does not start sshd in 1 out of 40 installs
Date: Tue, 12 Feb 2002 18:11:12 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-SAP: out
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g1CHC5w18356

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   patrick DOT hildenbrand AT sap DOT com
> http://www.saphosting.com


-----Original Message-----
From: Lassi A. Tuura [mailto:lassi DOT tuura AT cern DOT ch]
Sent: Dienstag, 12. Februar 2002 17:52
To: Hildenbrand, Patrick
Cc: 'cygwin AT cygwin DOT com'
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/