X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=VfVt10OSvHWoIvdUO1+GETb9tlwJ4fVdvoDkrzMFmixTQblcEpKrB
	eMdBxzn8dC9hG44jb9bO8R45xjBmBlgYNK1GzIJpueOeUEn3wRVWzvRDqB9lfNUY
	TV3TsRGfcdbC7ytFgML78ZIVwPYieR7hfpt19kskyOH+NsGMGIeyBU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=hIjLQXTt0N6moZ6HFYfJpARc4Ak=; b=rNJXsd1NdJ3S0aWDJ1cQv57XCBxq
	9lu5PaF3Fd+gmkndS7T3fOlVqLbFkaLwdiN2cRD7paXuoIacXzBYZ39qMATpBfBB
	oYQHCQYRzieKb6wU5DUDcCRPohQytorbN4Tyqmtdw079vPptjtWxgTVIhOPHFUxl
	87Od5MJuM3S70Sw=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO: calimero.vinschen.de
Date: Thu, 29 Jan 2015 10:34:50 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygrunsrv - services enters stopped state if underlying program exits or is killed - doesn't auto restart
Message-ID: <20150129093450.GB29242@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAEF1h+Wghm86TybnaLMz9TdX5NUV15aNBAC1KZ1dKhUOVZ-_Qg AT mail DOT gmail DOT com> <20150127090910 DOT GF14265 AT calimero DOT vinschen DOT de> <CAEF1h+XeFp_OCDNo-ok_EW=-1h94=mQRRz_ucZsix4wmow+WvQ AT mail DOT gmail DOT com> <20150128101833 DOT GX14265 AT calimero DOT vinschen DOT de> <CAEF1h+V75nQ3mo-ju+0VfhZu8=Wdp=+UwgpxxtGuvpuBTHt19g AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="LyciRD1jyfeSSjG0"
Content-Disposition: inline
In-Reply-To: <CAEF1h+V75nQ3mo-ju+0VfhZu8=Wdp=+UwgpxxtGuvpuBTHt19g@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

--LyciRD1jyfeSSjG0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Please, https://cygwin.com/acronyms/#TOFU
Thank you.

On Jan 28 17:38, Cary Lewis wrote:
> On Wed, Jan 28, 2015 at 5:18 AM, Corinna Vinschen
> <corinna-cygwin AT cygwin DOT com> wrote:
> > On Jan 27 15:02, Cary Lewis wrote:
> >> On Tue, Jan 27, 2015 at 4:09 AM, Corinna Vinschen
> >> <corinna-cygwin AT cygwin DOT com> wrote:
> >> --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?
> >
> > The patch is simple and I could upload a new cygrunsrv today or
> > tomorrow.
>=20
> That sounds like a plan, thanks Corinna.
>=20
> Do we need test how the service (program that cygrunsrv is running)
> exited? If --neverexits is present, it shouldn't care how it exited,
> it should just pass the fact that it exited unplanned to the SCM so
> that the recovery actions take place.

This is what happens now in 1.62-1 when it exited due to an unplanned
signal.

> It's only if cygrunsrv is the one that causes the 'service' to exit
> that the --neverexists shouldn't be considered.

That's when the termination or shutdown signal arrives.  Please give
cygrunsrv-1.62-1 a try.


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--LyciRD1jyfeSSjG0
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJUyf66AAoJEPU2Bp2uRE+gwF4P/1L11onUFUy0Y07fE0EPyB0r
XKWoEyVnjCWnn9OUbLJmI3XqmBKdL/We5WeXGbZtCxbCw++7WHx8omNqNzHAd5T/
HSBDaj7QEnBY+cMAOz9Nelb1nb1w9pG57TC3lrVIL+B/aSRAPLmn6FLw/E4qi//P
ne8pM2xaigLP8QpUNffQ7S3ji7tsCt3T78kLApkypdlbsGMl+0ceI/sUbltTL88o
O9bRkIjgi3lpdHY4GfICL+N6VBGsXp1V2Z7oW/fvTAhVm3nSrgv4CNniYMSXyMwD
H1z4zWx2maYCfBZJq/1o81fjxIrgxkxZWw0nzJ4D1iKWxg/3GONmg4fARZFJnS1T
mGJKHA9cY0wAC9DrXFHYSskO9zwiJagqcinQo4r/nWsxly8o/yYKYFkoaVaa/Izi
pralfgDXn7DSCPchb+707Hp2pvZCmat0zea+dTd6wfYgYfSoe81WqRlaCQUEeTcu
dvCnX1GY5I6+5M53pmN7k086n3Ljd2yMeUjmjlJlWopVNm1/CRYpznIJsPloOsHs
m4iZecCyp+bz+Gxab5ZSA0vdXQlUmpP+ZSK/ghtW2nV+MycuR/U0YO0pAEwBrETx
VqSMUwnrpFbtqpni48Gw9ZY0d/3hZ8lxyyRGp1a5bCDCC2XRPpZ5GkfxR49ndQjP
Ka7/DdaCHiDcfapMlQCx
=vz7/
-----END PGP SIGNATURE-----

--LyciRD1jyfeSSjG0--