From: Thomas Schwinge <schwinge-lists-skarnet.org-supervision@nic-nac-project.de>
Cc: Lars Kellogg-Stedman <lars@oddbit.com>, supervision@list.skarnet.org
Subject: Re: Respawn limit for runsv?
Date: Sun, 13 Feb 2005 22:21:45 +0100 [thread overview]
Message-ID: <20050213212145.GA1092@hera.lehmann.schwinge.homeip.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0502131334070.30064-100000@e-smith.charlieb.ott.istop.com>
On Sun, Feb 13, 2005 at 01:42:01PM -0500, Charlie Brady wrote:
> On Sat, 12 Feb 2005, Lars Kellogg-Stedman wrote:
> > - The disk fills up, causing your X startup to fail. But because of the
> > continuous respawning, you can't log in on the console!
This has happened to me, too. :-(
(And of course no telnetd, sshd or similar was running...)
> It would also be useful to have a mechanism to distinguish between a
> process dying in reponse to a request from runsv, and a program dying
> unexpectedly. Perhaps have "finish" and "unexpected_finish" scripts. I'd
> certainly like to have a mechanism to run a finish script if a service is
> taken down, but not if it just died unexpecedly. The "unexpected_finish"
> script could introduce the programmed delay you want, notify the admin,
> preserve any essential logs, etc.
I'd suggest to only have 'finish', but have it passed a) the information
how the process (was) terminated (i.e. either manually using svc,
runsvctrl, writing to 'SERVICE/supervise/control' or because of the
process's termination) and b) the process's exit-code. This information
could be passed either using positional parapeters or via environment
variables.
Regards,
Thomas
next prev parent reply other threads:[~2005-02-13 21:21 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 [this message]
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=20050213212145.GA1092@hera.lehmann.schwinge.homeip.net \
--to=schwinge-lists-skarnet.org-supervision@nic-nac-project.de \
--cc=lars@oddbit.com \
--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).