From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: Option for runsv/runsvdir to specify how many times to restart a service in a certain time period before giving up?
Date: Mon, 30 Oct 2006 09:51:43 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0610300949510.11426@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <20061030135834.GA26907@skarnet.org>
On Mon, 30 Oct 2006, Laurent Bercot wrote:
> Another approach to the throttle feature that doesn't require notification
> from runit would be to have a short-lived program, designed to be called in
> the finish script, that stores its information (last calling time ans such)
> in the filesystem. Maybe it's what you were thinking about. But I'm not
> sure how to make it reliable; storing short-lived information in the
> filesystem is very error-prone, that's the .pid way, which is precisely
> what supervision tools were designed to avoid.
The problem with pid files is race conditions. I don't see that as being a
problem here, as there is a single thread of execution between ./run and
./finish. ./finish should be able to reliably store whatever state it
needs in the file system. Or do you see something which I don't?
next prev parent reply other threads:[~2006-10-30 14:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 19:26 Alex Smith
2006-10-30 10:49 ` Alex Efros
2006-10-30 10:50 ` Alex Efros
2006-10-30 12:13 ` Dražen Kačar
2006-10-30 12:30 ` Alex Efros
2006-10-30 13:38 ` Laurent Bercot
2006-10-30 13:42 ` Alex Efros
2006-10-30 13:58 ` Laurent Bercot
2006-10-30 14:24 ` Alex Efros
2006-10-30 14:51 ` Charlie Brady [this message]
2006-10-31 0:48 ` Laurent Bercot
2006-10-30 18:49 ` Vincent Danen
2006-10-30 21:28 ` Alex Efros
2006-10-30 21:30 ` Vincent Danen
2006-10-30 17:52 ` Alex Smith
2006-10-30 21:41 ` Alex Efros
2006-11-01 12:01 ` Gerrit Pape
2006-11-01 12:17 ` Alex Efros
2006-10-30 18:49 ` Dražen Kačar
2006-10-30 22:03 ` Alex Efros
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.0610300949510.11426@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).