From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2630 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "Laurent Bercot" Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: [Announce] s6.rc: a distribution-friendly init/rc framework Date: Mon, 03 Jun 2019 16:06:04 +0000 Message-ID: References: <20180322132334.GA11596@caspervector> <20190603093041.GA10891@caspervector> Reply-To: "Laurent Bercot" Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="178530"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: eM_Client/7.2.34711.0 To: supervision@list.skarnet.org Original-X-From: supervision-return-2220-gcsg-supervision=m.gmane.org@list.skarnet.org Mon Jun 03 18:05:11 2019 Return-path: Envelope-to: gcsg-supervision@m.gmane.org Original-Received: from alyss.skarnet.org ([95.142.172.232]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1hXpSQ-000kIS-5y for gcsg-supervision@m.gmane.org; Mon, 03 Jun 2019 18:05:10 +0200 Original-Received: (qmail 23890 invoked by uid 89); 3 Jun 2019 16:05:33 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Original-Received: (qmail 23883 invoked from network); 3 Jun 2019 16:05:33 -0000 In-Reply-To: <20190603093041.GA10891@caspervector> X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduuddrudefjedgjeeiucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecupfgfoffgtffkveetuefngfdpqfgfvfenuceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfrhgfgggtgfesthhqredttderjeenucfhrhhomhepfdfnrghurhgvnhhtuceuvghrtghothdfuceoshhkrgdqshhuphgvrhhvihhsihhonhesshhkrghrnhgvthdrohhrgheqnecurfgrrhgrmhepmhhouggvpehsmhhtphhouhhtnecuvehluhhsthgvrhfuihiivgeptd Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2630 Archived-At: >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