Updated: cygrunsrv-0.92-2

Christopher Faylor cgf@redhat.com
Fri May 18 11:32:00 GMT 2001

On Fri, May 18, 2001 at 01:11:47PM -0500, Fred Yankowski wrote:
>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

It should be terminating.  You should not be seeing the looping behavior
unless your application is multithreaded.

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

I probably don't need to reiterate this, but I'd prefer "--termsig".


More information about the Cygwin-apps mailing list