supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Lars Kellogg-Stedman <lars@oddbit.com>
Subject: Re: Respawn limit for runsv?
Date: Sun, 13 Feb 2005 18:19:37 +0000 (UTC)	[thread overview]
Message-ID: <slrnd0v6lt.q8c.lars@flowers.house.oddbit.com> (raw)
In-Reply-To: <20050213134736.14448.qmail@d8e68f84add864.315fe32.mid.smarden.org>

> I also think a separate program is appropriate for such special
> services.

I'm not sure this should really be thought of as a special service; since
the supervisor is responsible for restarting the target program, this would
also seem to be the logical place to handle respawn limits.

Having said that, an external implementation does work, although the code
is a little more complicated since it becomes necessary to maintain some
sort of external state.  If the limiter were implemented in runsv, for
example, it could all be managed internally without the necessity of
reading and writing an external file.

But with a working external solution, I'm probably too lazy to pursue
anything else.

-- Lars

-- 
Lars Kellogg-Stedman <lars@oddbit.com>




  reply	other threads:[~2005-02-13 18:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11 12:56 Lars Kellogg-Stedman
2005-02-12  0:14 ` Charlie Brady
2005-02-12  1:14   ` Lars Kellogg-Stedman
2005-02-12  3:13     ` Charlie Brady
2005-02-12  5:21       ` Charles Duffy
2005-02-12 13:04         ` Lars Kellogg-Stedman
2005-02-13 18:42           ` Charlie Brady
2005-02-13 21:21             ` Thomas Schwinge
2005-02-13 13:48         ` Gerrit Pape
2005-02-13 18:19           ` Lars Kellogg-Stedman [this message]
2005-02-14 16:23             ` Clemens Fischer
2005-02-13  3:59     ` Lars Kellogg-Stedman

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=slrnd0v6lt.q8c.lars@flowers.house.oddbit.com \
    --to=lars@oddbit.com \
    /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).