From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: Laurent Bercot <ska-supervision@skarnet.org>
Cc: supervision@list.skarnet.org
Subject: Re: Incompatibilities between runit and s6?
Date: Thu, 11 Jan 2018 09:19:45 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.1801110914490.16098@e-smith.charliebrady.org> (raw)
In-Reply-To: <em54b6616e-4b46-40c5-8776-53f3cade30a1@elzian>
On Wed, 10 Jan 2018, Laurent Bercot wrote:
> >If you are a systemd user, chances are you do not need s6.
> >
> >Really? So all the criticism of systemd is bunkum?
>
> :) I need to update this page.
> What this means is that systemd does provide a supervision
> infrastructure, so for people stuck with systemd, it's okay to use what
> their system provides, and s6 is redundant there. This does not mean
> that all my systemd criticism is invalid.
>
> Also, admittedly, I simply did not want to read the systemd unit file
> documentation to understand how to start a s6 supervision tree from
> systemd. I will do the effort and come up with a small unit file
> suitable for this.
Thanks. I would rather you write one small unit file then me needing to
write ten or fifteen of them.
I agree with you about the systemd unit file documentation. That's exactly
why I still need runit or s6. Well, one of the reasons.
next prev parent reply other threads:[~2018-01-11 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 15:57 Charlie Brady
2018-01-10 19:49 ` Laurent Bercot
2018-01-11 14:19 ` Charlie Brady [this message]
2018-01-15 12:31 ` Laurent Bercot
2018-01-13 3:48 ` Jonathan de Boyne Pollard
2018-01-10 23:23 Avery Payne
2018-01-11 14:14 ` Charlie Brady
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=Pine.LNX.4.64.1801110914490.16098@e-smith.charliebrady.org \
--to=charlieb-supervision@budge.apana.org.au \
--cc=ska-supervision@skarnet.org \
--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).