From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: Laurent Bercot <ska-supervision@skarnet.org>
Cc: supervision@list.skarnet.org
Subject: Re: [announce] perp-2.03: persistent process supervision
Date: Mon, 14 Mar 2011 13:42:14 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1103141340330.12563@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <20110314170232.GB7248@skarnet.org>
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.
prev parent reply other threads:[~2011-03-14 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 10:39 Wayne Marshall
2011-03-14 13:17 ` Laurent Bercot
2011-03-14 14:02 ` Wayne Marshall
2011-03-14 14:23 ` Robin Bowes
2011-03-14 14:34 ` Wayne Marshall
2011-03-14 16:47 ` Laurent Bercot
2011-03-14 17:39 ` Wayne Marshall
2011-03-14 17:52 ` Paul Jarc
2011-03-14 18:43 ` Wayne Marshall
2011-03-14 18:34 ` Laurent Bercot
2011-03-14 15:03 ` Charlie Brady
2011-03-14 15:35 ` Wayne Marshall
2011-03-14 17:02 ` Laurent Bercot
2011-03-14 17:42 ` Charlie Brady [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.1103141340330.12563@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervision@budge.apana.org.au \
--cc=ska-supervision@skarnet.org \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).