From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: supervision@list.skarnet.org
Subject: Re: [Announce] s6.rc: a distribution-friendly init/rc framework
Date: Mon, 03 Jun 2019 16:06:04 +0000 [thread overview]
Message-ID: <em90a0a1e8-9ec3-44f7-8848-2273f6e11459@elzian> (raw)
In-Reply-To: <20190603093041.GA10891@caspervector>
>Assuming the number of syslog logging scripts is fairly small (a few for
>daemons in an anticipated list, and perhaps one for the rest; I think
>this scheme is actually already in use by most syslog users), what about
>setting up a group of s6-log consumer services, and use a chainloading
>program (akin to s6-tcpserver-access) with s6-ipcserver to dynamically
>decide which consumer to connect to (by interacting with s6rc-fdholder)?
Yes, that sounds good. Also, it feels similar to something I'm
proto-thinking about for instanced services ; I need to dwell on it
more, to see whether there are more common points.
Unfortunately, I don't have much time to work on it at the moment.
--
Laurent
next prev parent reply other threads:[~2019-06-03 16:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180322132334.GA11596@caspervector>
2018-03-22 17:10 ` Laurent Bercot
2018-03-23 4:00 ` Casper Ti. Vector
2018-03-23 10:09 ` slew: renamed from "s6.rc" Casper Ti. Vector
[not found] ` <20180323040022.GA1737@caspervector>
2018-03-23 10:51 ` [Announce] s6.rc: a distribution-friendly init/rc framework Laurent Bercot
2018-03-23 13:05 ` Alex Suykov
2018-03-23 13:31 ` Casper Ti. Vector
2018-03-23 14:19 ` Laurent Bercot
2018-03-23 13:20 ` Casper Ti. Vector
2018-03-25 4:57 ` Casper Ti. Vector
[not found] ` <20180323132058.GA21692@caspervector>
[not found] ` <20180325045750.GA5868@caspervector>
2018-03-25 6:38 ` Laurent Bercot
2018-03-25 9:31 ` Casper Ti. Vector
2019-06-03 9:30 ` Casper Ti. Vector
[not found] ` <20190603093041.GA10891@caspervector>
2019-06-03 16:06 ` Laurent Bercot [this message]
2018-03-22 13:23 Casper Ti. Vector
2018-03-22 15:29 ` Casper Ti. Vector
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=em90a0a1e8-9ec3-44f7-8848-2273f6e11459@elzian \
--to=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).