supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Dražen Kačar" <dave@fly.srk.fer.hr>
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 13:13:21 +0100	[thread overview]
Message-ID: <20061030121321.GA27602@fly.srk.fer.hr> (raw)
In-Reply-To: <20061030104923.GC32166@home.power>

Alex Efros wrote:
> 
> On Sat, Oct 28, 2006 at 08:26:27PM +0100, Alex Smith wrote:
> > Is this a good idea? Or not?
> 
> I think - no, it's a bad idea. Such ideas just make software bloated.

That kind of depends.

> Your services MUST run all of time, that's why they called services.
> If some service doesn't start - it's a big problem, and admin should be
> notified about it urgently and fix it (maybe by disabling this service :)).

Admin might not be available (admins have to sleep, after all). Besides,
the problem might be out of admin's control. For example, a remote
database (on which his service depends) doesn't work, or the network
connectivity was lost or something like that.

> Runit provide enough features to write such 'plugins' manually - you've
> ./finish file in which you can check how often it's executed and do
> something: stop service, sleep, or send sms to admin.

Sure, but if something's a common need for a large group of users, then
they call it a feature. Some of those who don't need such feature call it
a bloat, but I don't think that's a valid argument.

-- 
 .-.   .-.    Yes, I am an agent of Satan, but my duties are largely
(_  \ /  _)   ceremonial.
     |
     |        dave@fly.srk.fer.hr


  parent reply	other threads:[~2006-10-30 12:13 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 [this message]
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
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=20061030121321.GA27602@fly.srk.fer.hr \
    --to=dave@fly.srk.fer.hr \
    /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).