From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2086 Path: news.gmane.org!not-for-mail From: Charlie Brady Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: [announce] perp-2.03: persistent process supervision Date: Mon, 14 Mar 2011 13:42:14 -0400 (EDT) Message-ID: References: <20110314113933.3544df05@b0llix.net> <20110314131706.GA17316@skarnet.org> <20110314150225.7cf61c3c@b0llix.net> <4D7E24DA.2030404@robinbowes.com> <20110314170232.GB7248@skarnet.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: dough.gmane.org 1300124543 14909 80.91.229.12 (14 Mar 2011 17:42:23 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 14 Mar 2011 17:42:23 +0000 (UTC) Cc: supervision@list.skarnet.org To: Laurent Bercot Original-X-From: supervision-return-2320-gcsg-supervision=m.gmane.org@list.skarnet.org Mon Mar 14 18:42:18 2011 Return-path: Envelope-to: gcsg-supervision@lo.gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by lo.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1PzBma-0004VW-JX for gcsg-supervision@lo.gmane.org; Mon, 14 Mar 2011 18:42:16 +0100 Original-Received: (qmail 17458 invoked by uid 76); 14 Mar 2011 17:44:43 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 17445 invoked from network); 14 Mar 2011 17:44:43 -0000 X-X-Sender: charlieb@e-smith.charlieb.ott.istop.com In-Reply-To: <20110314170232.GB7248@skarnet.org> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2086 Archived-At: On Mon, 14 Mar 2011, Laurent Bercot wrote: > >> So, if I have a service that is normally running, ie. starts at boot, > >> but I have taken it down manually for whatever reason, and perpd dies, > >> then my service will also be re-started? > > > > And presumably the converse will apply as well. This is a problem with > > runit (and daemontools) - if a service has a 'down' file, but has been > > later started, a dying runsv (e.g. if killed by the OoM killer, or by a > > service which kills its process group) will be replaced by runsvdir, but > > the service will stay down. > > We've already discussed this. The default state of a service is controlled > by the absence or presence of a 'down' file. The actual state of a service > can be changed either manually or via a script, but this state *cannot be > strongly guaranteed* if it does not match the default. This is an > unavoidable limit of daemontools-like supervision schemes; do not blame it > on perp's design. I don't. I would just pointing it out, as one case of what can happen when state is in memory.