From: Steve Litt <slitt@troubleshooters.com>
To: supervision@list.skarnet.org
Subject: Re: External health Check Process
Date: Fri, 23 Oct 2020 13:03:55 -0400 [thread overview]
Message-ID: <20201023130355.6c575791@mydesk.domain.cxm> (raw)
In-Reply-To: <em34446e7c-4a87-4c70-a00a-b0b2851ebbc6@elzian>
On Fri, 23 Oct 2020 13:44:55 +0000
"Laurent Bercot" <ska-supervision@skarnet.org> wrote:
> >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.
>
> The thing is, s6 is a *process supervision* suite, so one s6
> "service" is really one long-running process. When you want health
> checks, you have two long-running processes: your daemon, and your
> health checker. So two s6 "services" is really the most elegant, most
> idiomatic and most natural solution.
>
> What you could have, on the other hand, is a s6-rc bundle, that
> contains
> both your daemon and your health checker: so you would be able to
> handle both the daemon and the health checker (2 longruns) with a
> single s6-rc/svctl command, using the name of the bundle.
>
> It's probably something that I can add to the next version of s6-rc:
> a command or an option to automatically add a health checker service
> to a longrun that is declared in the database, so you wouldn't have to
> write the health checker longrun manually. How does that sound?
I'd poll s6 users, and if less than 1/2 eagerly want this new feature,
I'd leave well enough alone.
SteveT
Steve Litt
Autumn 2020 featured book: Thriving in Tough Times
http://www.troubleshooters.com/thrive
prev parent reply other threads:[~2020-10-23 17:04 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
2020-10-23 9:15 ` Steve Litt
2020-10-23 13:44 ` Laurent Bercot
2020-10-23 17:03 ` Steve Litt [this message]
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=20201023130355.6c575791@mydesk.domain.cxm \
--to=slitt@troubleshooters.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).