DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=T+
	rgEvgTmWGhoIsX0hDt6ZSTZ9LzCX8hQ35Jw7l7BNHIUDx8r/h7sZFcGby+sRjK8d
	1rBsEXnAMmk6yK2dZRuy6VJNbSoQ2I3jD9OE2TbCKFo6NsjDtDvedZ5RlZH0+DzR
	8VBeYfUIkeGwxu+j1LVN+WhDcmuHQgqj2cqOEE33k=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <20150128115518.GZ14265@calimero.vinschen.de>
References: <CAEF1h+Wghm86TybnaLMz9TdX5NUV15aNBAC1KZ1dKhUOVZ-_Qg@mail.gmail.com>	<20150127090910.GF14265@calimero.vinschen.de>	<CAEF1h+XeFp_OCDNo-ok_EW=-1h94=mQRRz_ucZsix4wmow+WvQ@mail.gmail.com>	<20150128101833.GX14265@calimero.vinschen.de>	<20150128115518.GZ14265@calimero.vinschen.de>
Date: Wed, 28 Jan 2015 15:42:43 +0100
Message-ID: <CAO2ddnY+fk_CwGTZVyN7u6upZDxOrTbVjUVRCeGj8KBLEDPgig@mail.gmail.com>
Subject: Re: cygrunsrv - services enters stopped state if underlying program exits or is killed - doesn't auto restart
From: =?UTF-8?Q?Kizito_Porta_Balany=C3=A0?= <kfeina@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

2015-01-28 12:55 GMT+01:00 Corinna Vinschen <corinna-cygwin@cygwin.com>:
> On Jan 28 11:18, Corinna Vinschen wrote:
>> On Jan 27 15:02, Cary Lewis wrote:
>> > On Tue, Jan 27, 2015 at 4:09 AM, Corinna Vinschen
>> > --neverexits works, but not if the program that cygrunsrv starts is
>> > stopped with a kill -9 signal. Perhaps the -9 signal propagates to the
>> > cygrunsrv.exe program?
>>
>> Hmm, yes.  Cygrunsrv evaluates how the service process ended, and only
>> if it exited the neverexits logic comes into play.  If it ended due to
>> a signal, it does nothing.
>>
>> This is unfortunate because it diminishes the usefulness of --neverexits.
>> I could patch cygrunsrv to do this:
>>
>>   If the service exited due to a signal, and if that signal is not the
>>   defined termination or shutdown signal (default SIGTERM for both),
>>   and if --neverexits has been defined, then performas the neverexits
>>   action.
>>
>> Does that sound ok?

I would say that this should be the default behavior:

If the signal is SIGTERM and the service is configured to restart the
program, then restart the program.

So, --neverxits should be the default behaviour of cygrunsrv , so
--neverexists shouldn't exist as an option. :) But perhaps I'm wrong
and I don't understand completely the problem.

Thanks for your time.

>> The patch is simple and I could upload a new cygrunsrv today or tomorrow.
>
> https://cygwin.com/ml/cygwin-announce/2015-01/msg00041.html
>
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Maintainer                 cygwin AT cygwin DOT com
> Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple