supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Scott Colby" <>
To: "Alex Efros via supervision" <>
Subject: Supervision on the BSD's
Date: Sat, 09 Apr 2022 01:38:56 -0400	[thread overview]
Message-ID: <> (raw)


I'm planning to set up a router on an old x86 box with a couple of
NIC's for the fun/experience of it. I'm looking at using one of the
BSD's as the operating system, since I haven't used those before.

I started looking at how to configure daemons/services on OpenBSD
and FreeBSD and am a little surprised at what I found. As far as I
can tell, OpenBSD's rc assumes that services will background
themselves and does no supervision at all. It seems like FreeBSD's
daemon(8) has some supervision capabilities with the -r flag, but
it is unclear to me how widely used that is.

Given the apparently poor state of supervision, I'm considering
using s6 when I configure this system.

In searching, I found some messages on the Skaware lists about
running s6 as PID 1 on FreeBSD; has that work been published anywhere?
I'm not sure if I want to go so far as replacing PID 1 right out
of the gate, but having some existing service directories would be

Have I correctly understood how daemons/services work on the BSD's?
If not, what am I missing? Are the daemons included with the
distributions so incredibly stable that they don't need supervision
in order to keep the system functional?

Finally, if you wanted to create a router that you could (metaphorically)
put in a closet and forget about for 5 years, what approach would
you take? My initial thought was OpenBSD + s6, but I worry now that
there could be an impedance mismatch between these systems.

Any thoughts people have on this will be greatly appreciated.

Scott Colby

             reply	other threads:[~2022-04-09  5:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09  5:38 Scott Colby [this message]
2022-04-09  7:57 ` Alexis
2022-04-09 11:36 ` Ramarro Marrone
2022-04-10 18:56   ` Oliver Schad
2022-04-09 13:43 ` Laurent Bercot
2022-04-11 17:18 ` J. Lewis Muir

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).