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: Thu, 17 May 2001 22:28:23 +0200
From: Corinna Vinschen <cygwin AT cygwin DOT com>
To: cygwin <cygwin AT cygwin DOT com>
Subject: Re: Suiqd as service [was: Re: New on sources: cygrunsrv-0.92]
Message-ID: <20010517222823.Y31266@cygbert.vinschen.de>
Mail-Followup-To: cygwin <cygwin AT cygwin DOT com>
References: <001001c0dec3$d975aa10$0200a8c0 AT lifelesswks>; <20010517144144 DOT U31266 AT cygbert DOT vinschen DOT de> <3B042140 DOT 25755 DOT 9CB4883 AT localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3B042140.25755.9CB4883@localhost>; from gerrit.haase@t-online.de on Thu, May 17, 2001 at 07:06:40PM +0200

On Thu, May 17, 2001 at 07:06:40PM +0200, Gerrit P. Haase wrote:
> system to access them. Thats it (with squid), but it works not with 
> Apache. 
> 
> There is NO error message in sys/event log.
> Only two messages:
> 
> 1:
> Cygwin Apache : Win32 Process Id = 0xFE : Cygwin Process Id = 0xFE :
>  `Cygwin Apache' service started.
> 
> 2:
> Cygwin Apache : Win32 Process Id = 0xFE : Cygwin Process Id = 0xFE :
>  `Cygwin Apache' service stopped.
> 
> No error...
>
> However, httpd is running.

Which probably means that apache has forked a daemon.

> You also wrote, it couldn't be killed, if a daemon forks and the parent
> dies, but that is not absolutely correct. Cygrunsrv is listed as a task
> and cygrunsrv could be killed, so the process it invokes dies, too.

? You're mixing two different things. Either the application forks/exits
and cygrunsrv behaves as above. In that case there's no cygrunsrv process.
Or the child app doesn't fork and you should not kill cygrunsrv but send
a stop message by calling `cygrunsrv -E <svcname>' or `net stop <svcname>'.
In that case, cygrunsrv sends a SIGTERM to it's child application to
give it a chance to close it's service gracefully. Killing cygrunsrv
is somewhat violent.

Corinna

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

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple