Re: staggering runsv startup

From: Steve Litt <>
Date: Fri, 5 Jun 2015 10:23:39 -0400

On Thu, 4 Jun 2015 17:46:29 -0700
James Powell <> wrote:

> If runit had the ability to order processes like OpenRC where you
> have:
> before=
> after=
> setups, you could order the entire tree structure.
> The problem with sv check is the command often can only check the
> status of the service.

Hi James,

Specific ordering is sorely missing in the daemontools inspired
tools. This has nothing to do with sv check: They're two different

Ordering is what you have in a non-parallel startup: Do them in a
specific order. It's what you accomplish with the numbering for
SysVinit in the /etc/rc.d/rc3.d symlinks. sv check and checking in
general is about process dependencies, not order. One does not eliminate
the need for the other. If the network doesn't come up during its turn,
you don't want to start sshd later, even though your *attempt* at the
network came several seconds before your attempt at sshd.

Where ordering aids dependencies is that it makes it likely that your
services will fire right up, instead of repeatedly (and
indeterminately) failing for lack of a dependency.


Steve Litt
June 2015 featured book: The Key to Everyday Excellence
Received on Fri Jun 05 2015 - 14:23:39 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:44:19 UTC