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
Date:	Tue, 11 Mar 2003 16:51:27 +0000 (GMT Standard Time)
From:	Max Bowsher <maxb AT ukf DOT net>
To:	cygwin AT cygwin DOT com
cc:	Guillaume Devoyon <guillaume DOT devoyon AT integro-networks DOT com>
Subject:	RE: init.d
In-Reply-To:	<Pine.GSO.4.44.0303111140170.11568-100000@slinky.cs.nyu.edu>
Message-ID:	<Pine.WNT.4.53.0303111649280.288@pcchem101.chem.pwf.cam.ac.uk>
References:	<Pine DOT GSO DOT 4 DOT 44 DOT 0303111140170 DOT 11568-100000 AT slinky DOT cs DOT nyu DOT edu>
X-X-Sender:	mob22 AT imap DOT hermes DOT cam DOT ac DOT uk
MIME-Version:	1.0

On Tue, 11 Mar 2003, Igor Pechtchanski wrote:

> IIRC, cygrunsrv expects the program it's starting to fork
> itself and exit with an appropriate return code within a certain time
> window.  Otherwise it times out and says "the service could not be started
> proprely".  sshd and httpd (and some others as well) have an option to
> fork and exit -- see if webmin has one as well.

I think you've got that backwards. Cygrunsrv expects the process to *not*
fork and exit, and the sshd/httpd/rsyncd options are for *preventing*
the usual fork and exit.

Max.


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