From: Oliver Schad <oliver.schad@automatic-server.com>
To: supervision@list.skarnet.org
Subject: Re: External health Check Process
Date: Fri, 23 Oct 2020 09:27:53 +0200 [thread overview]
Message-ID: <20201023092753.517078df@flunder> (raw)
In-Reply-To: <20201022200317.52224023@mydesk.domain.cxm>
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
On Thu, 22 Oct 2020 20:03:17 -0400
Steve Litt <slitt@troubleshooters.com> wrote:
> But most of the other suggestions that in my opinion are just answers
> to systemd weenie's "but s6 doesn't have _____" arguments, and don't
> add nearly enough functionality or convenience for the complexity, or
> just plain size added to the user manual, to justify.
>
> The OP already stated there's a way to do it currently. Why complexify
> s6 to do something already doable?
I just miss the elegance of the solution: I personally want to model
one service with one s6 service. For me it would mean thinking about a
wrapper around s6 to get that. Maybe I get now the slew thing.
And it's ok to need a wrapper to get useability, but the
advertisement of that should be better on the website that you SHOULD
use that wrapper (and for me this wrapper should be part of the s6
project).
Best Regards
Oli
--
Automatic-Server AG •••••
Oliver Schad
Geschäftsführer
Turnerstrasse 2
9000 St. Gallen | 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:[~2020-10-23 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 12:28 Oliver Schad
2020-10-22 15:34 ` Laurent Bercot
2020-10-22 15:46 ` Casper Ti. Vector
2020-10-23 0:03 ` Steve Litt
2020-10-23 7:27 ` Oliver Schad [this message]
2020-10-23 9:15 ` Steve Litt
2020-10-23 13:44 ` Laurent Bercot
2020-10-23 17:03 ` Steve Litt
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=20201023092753.517078df@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).