From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2304 Path: news.gmane.org!.POSTED!not-for-mail From: "Laurent Bercot" Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: Incompatibilities between runit and s6? Date: Wed, 10 Jan 2018 19:49:06 +0000 Message-ID: References: Reply-To: "Laurent Bercot" NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1515613637 21256 195.159.176.226 (10 Jan 2018 19:47:17 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 10 Jan 2018 19:47:17 +0000 (UTC) User-Agent: eM_Client/7.1.31849.0 To: supervision@list.skarnet.org Original-X-From: supervision-return-1895-gcsg-supervision=m.gmane.org@list.skarnet.org Wed Jan 10 20:47:13 2018 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.84_2) (envelope-from ) id 1eZML1-0004ew-UW for gcsg-supervision@m.gmane.org; Wed, 10 Jan 2018 20:47:04 +0100 Original-Received: (qmail 30933 invoked by uid 89); 10 Jan 2018 19:49: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: Original-Received: (qmail 30926 invoked from network); 10 Jan 2018 19:49:33 -0000 In-Reply-To: X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedtuddrkeekgddufedtucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecupfgfoffgtffkveetuefngfdpqfgfvfenuceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfrhgfgggtgfesthhqredttderjeenucfhrhhomhepfdfnrghurhgvnhhtuceuvghrtghothdfuceoshhkrgdqshhuphgvrhhvihhsihhonhesshhkrghrnhgvthdrohhrgheqnecurfgrrhgrmhepmhhouggvpehsmhhtphhouhhtnecuvehluhhsthgvrhfuihiivgeptd Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2304 Archived-At: >Has anyone tabulated technical differences between runit and s6? I'm >considering migrating some systems which use runit to supervise some of >their services (systemd the others - they're CentOS based). I am=20 >wondering >whether I can write a wrapper caled "sv" which calls s6-svc with the >appropriate argument rewriting, to avoid needing to find and modify=20 >many >scripts. Has anyone written such an 'sv' command already? I'm not aware of such a command, but s6-svc supports everything sv does, so writing such a script should not be hard. The only difficulty is if the service uses a ./check file, which "sv start" supports natively but s6-svc does not, so the wrapper would need to perform the ./check polling itself; but the best thing to do in this case is to rewrite the run script to use s6-notifyoncheck, so the check automatically uses the s6 readiness notification framework. >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. -- Laurent