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
Date:	Fri, 30 Nov 2001 11:16:50 +0100
From:	Corinna Vinschen <cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: cygrunsrv sshd fails: Some clues
Message-ID:	<20011130111650.R24007@cygbert.vinschen.de>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20011120080121 DOT 02440440 AT pop DOT gmx DOT li> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20011120190516 DOT 02561e50 AT pop DOT gmx DOT li> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20011129105747 DOT 0235c638 AT localhost> <3C0672B4 DOT 8050404 AT cportcorp DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20011130040938 DOT 0239a360 AT localhost>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<5.1.0.14.2.20011130040938.0239a360@localhost>; from sbehrens@gmx.li on Fri, Nov 30, 2001 at 04:24:54AM -0500

On Fri, Nov 30, 2001 at 04:24:54AM -0500, Shawn Behrens wrote:
> service called sshd (which already existed), so the sshd service now has a 
> 'Description'. I can't see that there were any other changes to the 
> service;  which doesn't mean there weren't any, of course, just that I 
> can't see them.
> 
> Could some of the gals and guys who have the same problem try adding a 
> Description to the service via regedit, see whether it starts up then?

What other people with problems starting these service can try is to
add a dependency to another service as e.g. tcpip.  This could
positively influence the load order of the services.  Perhaps they are
just started too early.

> I do notice that while sshd has cygrunsrv as the executable, inetd lists 
> itself (c:\cygwin\usr\sbin\inetd.exe) as the executable to be started as a 
> service. Is this the way it's supposed to be? Shouldn't inetd also use 
> cygrunsrv?

Inetd has been ported many moons before cygrunsrv came to existence.
So it has the NT service handling code builtin.

It's a good question, though.  I'm not quite sure if we shouldn't
better revert these NT service stuff from inetd and use cygrunsrv
to start it.  It's way cleaner a solution.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
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 -