From: Oliver Schad <oliver.schad@automatic-server.com>
To: supervision@list.skarnet.org
Subject: Re: Supervision on the BSD's
Date: Sun, 10 Apr 2022 20:56:19 +0200 [thread overview]
Message-ID: <20220410205619.4c9c59a3@flunder> (raw)
In-Reply-To: <ee8d124d-cf6f-4e7b-89c6-3d66889d094c@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
On Sat, 09 Apr 2022 11:36:35 +0000
"Ramarro Marrone" <rm@allmail.net> wrote:
> I too had been surprised by the lack of supervision in OpenBSD.
> > Are the daemons included with the
> > distributions so incredibly stable that they don't need supervision
> > in order to keep the system functional?
>
> Yes
It's just a question of chance and big numbers. So if you're
responsible for a big fleet of things and you have costs to handle
every failure, it makes sense to have supervision to reduce these costs.
Most users with a few machines never observed any failure ever,
independent of the operating system and (server) software.
If this would be the argument to decide if supervision is necessary,
nobody would need it.
And yes, the BSD world tries to be conservative compared to Linux and
yes, OpenBSD tends to be the most conservative BSDs related to changes.
But I think that isn't the most important thing for decision.
I.e. your super stable BSD doesn't help against DoS attacks (read as
overload), unstable hardware, misconfiguration of services, packet
loss, ...
Best Regards
Oli
--
Automatic-Server AG •••••
Oliver Schad
Geschäftsführer
Hardstr. 46
9434 Au | Schweiz
www.automatic-server.com | oliver.schad@automatic-server.com
Tel: +41 71 511 31 11 | Mobile: +41 76 330 03 47
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2022-04-10 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 5:38 Scott Colby
2022-04-09 7:57 ` Alexis
2022-04-09 11:36 ` Ramarro Marrone
2022-04-10 18:56 ` Oliver Schad [this message]
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:
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=20220410205619.4c9c59a3@flunder \
--to=oliver.schad@automatic-server.com \
--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).