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
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<5.2.0.9.2.20030218100657.01da6858@pop3.cris.com>
X-Sender:	rrschulz AT pop3 DOT cris DOT com
Date:	Tue, 18 Feb 2003 10:12:49 -0800
To:	cygwin AT cygwin DOT com
From:	Randall R Schulz <rrschulz AT cris DOT com>
Subject:	Re: error setting up ipc-daemon
In-Reply-To:	<Pine.GSO.4.44.0302181257400.7773-100000@slinky.cs.nyu.edu>
References:	<5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030218080515 DOT 02ee9710 AT pop3 DOT cris DOT com>
Mime-Version:	1.0

Igor,

I was under the impression that the currently recommend way to get 
inetd running as a cygwin service was this:

     inetd --install-as-service

The resulting Windows service does not use cygrunsrv to invoke 
inetd--it is launched directly:

Path to executable: D:\cygwin\usr\sbin\inetd.exe

Randall Schulz


At 10:01 2003-02-18, Igor Pechtchanski wrote:
>Randall,
>
>An excerpt from "cygrunsrv --help" below
>
>   -e, --env <VAR=VALUE>     Optional environment strings which are added
>                             to the environment when service is started.
>                             You can add up to 255 environment strings using
>                             the `--env' option.
>                             Note: /bin is always added to $PATH to allow all
>                             started applications to find at least 
> cygwin1.dll.
>
>shows that you shouldn't really need to add c:\cygwin\bin to your system
>path (if one uses cygrunsrv, that is).  If that is not the case, then it's
>a bug in cygrunsrv (or an error in documentation).
>     Igor
>
>On Tue, 18 Feb 2003, Randall R Schulz wrote:
>
> > Daya,
> >
> > When I recently installed Cygwin anew on a system not my own and wanted
> > to enable the Cygwin inetd, I had what might be the same problem. One
> > thing that tipped me off was the fact that although the message was
> > about the service not starting up "in a timely fashion," the failure
> > occurred essentially immediately upon my attempt to manually start the
> > service.
> >
> > It turned out that the system-wide PATH must contain the directory
> > holding the Cygwin1.dll. I think that's because inetd is in /usr/sbin
> > and Cygwin1.dll is in /bin (a.k.a. /usr/bin). Were they in the same
> > directory, I don't think a PATH addition would be required to locate
> > dependent DLLs.
> >
> > You'll also want to make sure that all your Cygwin mounts are system
> > mounts, or they won't be seen by inetd and it may not be able to find
> > other files it needs
> >
> > Randall Schulz
> >
> > At 06:31 2003-02-18, Daya Kiran Sunkara wrote:
> > >Hi
> > >I am trying to run ipc-daemon as a service under
> > >windows xp. But i get the following error message
> > >"Error 1053: The service did not respond to the start
> > >or control request in a timely fashion"
> > >
> > >Can anyone please explain me what this means!!!
> > >Bye
> > >Daku


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