supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: Respawn limit for runsv?
Date: Fri, 11 Feb 2005 22:13:43 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0502112204500.16754-100000@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <lars-744DA8.20145611022005@sea.gmane.org>


On Fri, 11 Feb 2005, Lars Kellogg-Stedman wrote:

> > Do you have any concrete example that illustrates the "problem".
> 
> Thanks, but I'm looking at providing a solution to a general class of 
> problems.

There is no general class of problem unless you can provide a single 
instance.

>  My question is simply whether or not anyone has investigated 
> adding this sort of feature to runsv before -- if not, I'll probably 

Why would they, if there isn't a real problem?

> spend some of my time trying to add this behavior, since respawning 
> software is a reasonably common problem (for example, this is why the 
> SysV Init package under Linux will stop respawning a process for a few 
> minutes in this situation).

One of the reasons people chose to use daemontools (and subsequently 
runit) was to get away from such ad-hoc behaviour ...

You say that respawning software is a reasonably common problem. Whenever 
I've seen it, it was a configuration problem. Or rather, there was a 
configuration problem, and the respawning was a symptom. I didn't see the 
respawning as a problem. The automated respawning is a feature.

You asked for thoughts. I've given them.

---
Charlie



  reply	other threads:[~2005-02-12  3:13 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 [this message]
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
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=Pine.LNX.4.44.0502112204500.16754-100000@e-smith.charlieb.ott.istop.com \
    --to=charlieb-supervision@budge.apana.org.au \
    --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).