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>
Subject: Re: runit/dependencies
Date: Mon, 12 Jan 2004 10:41:15 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0401121028530.7437-100000@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <20040112142913.14952.qmail@ccf32c333c9930.315fe32.mid.smarden.org>


On Mon, 12 Jan 2004, Gerrit Pape wrote:

> Regarding all these ``I need support for dependencies'' (I've been asked
> often), and even work to provide straight dependencies with runit[0],
> I've yet to see a real example that cannot be handled by runit as it is
> currently.  It works for me.  All a service needs to do if another
> service it depends on isn't available, is to fail.

The key word here is "available". The exact semantics of "available" will
vary from service to service. The best that runit can provide is "has been
asked to start and hasn't failed yet". A service run script, OTOH, can
perform arbitrary probes of the "availability" of other services on which
it depends.

I consider the limited semantics of the status provided by "runsvstat" to
be a fatal obstacle to attempts to build dependency management into runit.  
All you can achieve is a slightly ordered parallel startup of multiple
services, with race conditions determining whether or not services start
successfully.

--
Charlie



  reply	other threads:[~2004-01-12 15:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1AVGpa-00036Z-00@scice>
     [not found] ` <20031215092044.6006.qmail@1e2dfc267734fe.315fe32.mid.smarden.org>
2004-01-08 11:13   ` runit/dependencies Nico Schottelius
2004-01-12 14:25     ` runit/dependencies Gerrit Pape
2004-01-12 15:41       ` Charlie Brady [this message]
2004-01-18 15:45         ` runit/dependencies Gerrit Pape
2004-05-07  2:53           ` runit/dependencies Kevin P. Fleming
2004-05-08  9:54             ` runit/dependencies Alex Efros
2004-05-08 14:00               ` runit/dependencies Kevin P. Fleming
2004-05-08 22:01                 ` runit/dependencies Charlie Brady
2004-05-09 14:33                   ` runit/dependencies Kevin P. Fleming
2004-05-10  3:13                     ` runit/dependencies Charlie Brady
2004-05-08 17:22             ` runit/dependencies Gerrit Pape
2004-05-09 14:30               ` runit/dependencies Kevin P. Fleming
2004-05-10  3:04                 ` runit/dependencies George Georgalis
2004-05-10 15:14                 ` runit/dependencies Gerrit Pape
2004-05-10 22:57                   ` runit/dependencies Kevin P. Fleming
2004-05-10 23:20                     ` runit/dependencies Charlie Brady
2004-05-11 18:22                       ` runit/dependencies Kevin P. Fleming
2004-05-11 19:18                         ` runit/dependencies Charlie Brady
2004-05-12  0:13                           ` runit/dependencies Kevin P. Fleming
2004-05-11 18:27                       ` runit/dependencies Kevin P. Fleming
2004-05-11 18:44                         ` runit/dependencies Charlie Brady
2004-05-11 17:46                     ` runit/dependencies Gerrit Pape
2004-05-11 18:36                       ` runit/dependencies Kevin P. Fleming
2004-05-11 18:57                         ` runit/dependencies 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.44.0401121028530.7437-100000@e-smith.charlieb.ott.istop.com \
    --to=charlieb-supervision@budge.apana.org.au \
    /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).