From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: Supervision Mailing List <supervision@list.skarnet.org>
Subject: Compatibilities between runit and s6 (re: Incompatibilities between runit and s6?)
Date: Sat, 13 Jan 2018 13:03:24 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.1801131252340.24948@e-smith.charliebrady.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1801110910410.16098@e-smith.charliebrady.org>
On Thu, 11 Jan 2018, Charlie Brady wrote:
> On Wed, 10 Jan 2018, Avery Payne wrote:
>
> > I am guessing the differences will be subtle, and most of the general
> > behavior you desire will remain the same. You may be able to get a way
> > with a "sed 's/sv\ /s6-sv\ /' <old-script-name >new-script-name" on some of
> > your scripts; give it a try, what could it hurt?
>
> That would fail because, eg, 'sv t xxx' needs to become 's6-svc -t xxx'.
I've started thinking that I wouldn't need to abandon use of 'sv'. With
both runit and s6 installed, and a supervision tree of s6-svscan and
s6-supervise processes, I suspect that 'sv t ...' would still work. 'sv
status ...' on the other hand might not. I would need to study the control
fifo protocol and status file layout to be sure.
Again, has anyone else considered these things and can offer an opinion?
Are the differences documented anywhere? There is a certain level of
compatibility between daemontools and runit, and I presume the same exists
for s6. The devil is in the detils.
next prev parent reply other threads:[~2018-01-13 18:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 23:23 Incompatibilities between runit and s6? Avery Payne
2018-01-11 14:14 ` Charlie Brady
2018-01-13 18:03 ` Charlie Brady [this message]
2018-01-13 18:55 ` Compatibilities between runit and s6 (re: Incompatibilities between runit and s6?) Laurent Bercot
2018-01-14 11:36 ` Jonathan de Boyne Pollard
2018-01-14 21:08 ` Charlie Brady
2018-01-14 21:54 ` Jonathan de Boyne Pollard
2018-01-15 12:53 ` Thomas Caravia
2018-01-15 13:33 ` Laurent Bercot
2018-01-16 0:33 ` Charlie Brady
2018-01-16 0:44 ` nosh build problems (Re: Compatibilities between runit and s6 (re: ) Charlie Brady
2018-01-16 16:09 ` Charlie Brady
2018-01-16 20:51 ` Jonathan de Boyne Pollard
2018-01-17 1:26 ` Guillermo
2018-01-17 7:35 ` Jonathan de Boyne Pollard
2018-01-17 15:25 ` Charlie Brady
2018-01-18 11:58 ` Guillermo
2018-01-18 14:25 ` nosh build problems (Re: Compatibilities between runit and s6 Charlie Brady
2018-02-18 21:16 ` nosh build problems (Re: Compatibilities between runit and s6 (re: ) Guillermo
2018-01-16 8:10 ` Compatibilities between runit and s6 (re: Incompatibilities between runit and s6?) Jonathan de Boyne Pollard
2018-01-16 15:59 ` Charlie Brady
2018-01-16 21:51 ` Jonathan de Boyne Pollard
2018-01-16 8:06 ` Jonathan de Boyne Pollard
2018-01-16 14:52 ` multiplexd
[not found] ` <89cffa18-a72a-ed98-031c-c72fc00ad5aa@ntlworld.com>
2018-01-16 15:44 ` Laurent Bercot
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.1801131252340.24948@e-smith.charliebrady.org \
--to=charlieb-supervision@budge.apana.org.au \
--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).