Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
X-Authentication-Warning: shell-3.enteract.com: fcy set sender to fred AT ontosys DOT com using -f
Date: Fri, 18 May 2001 13:11:47 -0500
From: Fred Yankowski <fred AT ontosys DOT com>
To: cygapp <cygwin-apps AT cygwin DOT com>
Subject: Re: Updated: cygrunsrv-0.92-2
Message-ID: <20010518131146.A50378@enteract.com>
References: <20010517161408 DOT A60686 AT enteract DOT com> <20010518101617 DOT B31266 AT cygbert DOT vinschen DOT de> <20010518103001 DOT A61059 AT enteract DOT com> <20010518182956 DOT D31266 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010518182956.D31266@cygbert.vinschen.de>; from cygwin-apps@cygwin.com on Fri, May 18, 2001 at 06:29:56PM +0200

On Fri, May 18, 2001 at 06:29:56PM +0200, Corinna Vinschen wrote:
> As a result, the current method isn't sufficient for shutdown since the
> service thread simply hangs in `waitpid' until the child application
> actually exited.

OK, we'll have to consider a different design there.  I've been able
to get by with a simple waitpid design in postgres so far, but that
might be fragile, dependent on processor speed and whatnot.

> I'm somewhat surprised. When I send SIGTERM to cygrunsrv, the signal
> is silently ignored and cygrunsrv grabs all CPU time it can get.

Ah, sorry, I was basing my statement on the code and not on actual
tests.  I've found that I need to ignore SIGHUP (with SIG_IGN) in the
postgres service process; if I don't, that service process seems to
stop running abruptly in the middle of NT shutdown.  I thought the
process was terminating, but it might instead be looping as you have
seen.

> Currently we have the following TODO list:
> 
> * --sig <signal> option.
> * --std{in,out,err} option as described in the cygwin mailing list.
> * --dep(?) option for adding dependencies to other services.

OK, I'll start with '--sig' and then look into '--dep'.

> * (not yet possible): Sending signals to cygrunsrv to perform various
>   actions.

That one is not important to me.  What actions would we want beyond
the effect of 'net stop'?

-- 
Fred Yankowski           fred AT OntoSys DOT com      tel: +1.630.879.1312
Principal Consultant     www.OntoSys.com       fax: +1.630.879.1370
OntoSys, Inc             38W242 Deerpath Rd, Batavia, IL 60510, USA