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 19:14:21 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0502111910430.16754-100000@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <lars-E5D74A.07564511022005@sea.gmane.org>
On Fri, 11 Feb 2005, Lars Kellogg-Stedman wrote:
> Has anyone investigated adding some sort of respawn limiter to runit? I
> figure that if a program is crashing immediately every time it runs, it
> probably doesn't need to be restarted -- which just floods the logs with
> error message, perhaps overwriting critical log data about what
> precipitated the problem in the first place.
The problem is obviously ongoing, and will be able to be diagnosed without
earlier logs. Certainly the direct cause will be diagnosable. If there's
an indirect cause, it won't necessarily be logged in this process's log
files.
Do you have any concrete example that illustrates the "problem". I
wouldn't be happy to see additional complexity without strong
justification.
---
Charlie
next prev parent reply other threads:[~2005-02-12 0:14 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 [this message]
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
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.0502111910430.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).