From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2586 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: multiplexd Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: what init systems do you use ? Date: Mon, 13 May 2019 20:13:29 +0100 Message-ID: <20190513191328.uf4lvqvuaw5e6qat@flywheel> References: <11997211556565598@myt6-27270b78ac4f.qloud-c.yandex.net> <15692301556844801@iva7-b6ed732000ae.qloud-c.yandex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="215624"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: NeoMutt/20170113 (1.7.2) To: supervision@list.skarnet.org Original-X-From: supervision-return-2176-gcsg-supervision=m.gmane.org@list.skarnet.org Mon May 13 21:14:12 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 1hQGOo-000tuK-U2 for gcsg-supervision@m.gmane.org; Mon, 13 May 2019 21:14:11 +0200 Original-Received: (qmail 31571 invoked by uid 89); 13 May 2019 19:14:30 -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 31564 invoked from network); 13 May 2019 19:14:29 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1557774837; bh=vramczefsKfRgL+D0kYtIlTnVJSE6L7Bsr+AkOXe/Kc=; h=X-UI-Sender-Class:Date:From:To:Subject:References:In-Reply-To; b=FwKeJDf70CyULYDCiU2xjCG07PlLl1k/B171IFhMkjGEK8cs2tWnp9zEob/iPCSyg 87Z6+J7xOUCQYFk266UYICFTh0cAneLm92DUuzD8tXANS4kT5JFBULuo5zPXTqlPiQ zqdz9WMU5FT0VXQjMPP/CHg+YXY88GQaAqv0ujN4= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Content-Disposition: inline In-Reply-To: <15692301556844801@iva7-b6ed732000ae.qloud-c.yandex.net> X-Provags-ID: V03:K1:h0ir653Pa9y03AtMQNiCoJ+HBtZkiE59pTmKMXC0O9W29ClWmOn xh/sE2GrkfbwFWcUxLZlU+nbPNaPKlxQWjo9zhl/ttHor0DygdfIL/YEE6wOvU5Z5yHLMTp OSSSLQmWggsbguI67u5ixqnQZWCParxBbF2KvJzCcNbM3b4hLkCO3wxl4jI76ituFwO2OdL XxWNpJuLWWCawaSFYMWxw== X-UI-Out-Filterresults: notjunk:1;V03:K0:EEEGuD+0ifg=:d+ckOlzJB7ImKMV9rUyM+g AN1qSk+F4bD2osIJzCgvXboBBFIXj2/+qgP04rmprRUzawn+TURN9NFDH88hjEwO+JauGkJsu VUU9yprgwEnkic2lXcIt2PTKLVBkOWTgQt/mf2SKq939Xp0H2WGsIp+vw0Kr5dH/H1xqqjFPK KXK5y0Y3xhjtlHcKjzfGff68oCLqbzc6c/GZnz4+0gx1PNk74RG7ECV0+AzJUOHcLqGLF+AR5 zk6SCzEZBkv66RzoxZnovsNFUVrw0+N8aXjj+jep2MyBn45BFLYeBb8koShMAhuIXFgi9PNCR Ua0CkO1jvbQ5HcuMcqzWwMl/qtXysoh38vJvD6H6s3IZlTzyCOtHLxh8uE2BFHSXytXebxj3m IQEfS+BnWz2YgOgH5oEJWOedFaJQxg7XiVS1d3OSXyoL97LztNJs2+9GTk5LVVdQsVRda8l9W aw+Hn1WvDSMm+n5xyIvzwIPx/20WJ2e9v3hRA4WsUS80iau+s/lRyqSUge2UkgSfPg14W3cKD wxVb13lR3+0pCW7MF1wM6/Oav+bfovFG+bKP56jUM8q8t+TF1BcXbCkfsaJglT4iFUD2avbz9 sUdVTCSDdSp82eliviU5WtiF0qrtFipHaT1WS7QLvBEF4Z/3qC8zu/5oT61NCKIpeqGWCcbld N1QT+yDA93Frwb9QnEls8db1gxHrHxauZpGgY365kWSVtEtqH3brFKOQI0xZf+ioTsm7zjn6l C0kxtmJ1Waj6vuDIsVEZSeOu441JXOZ5oM+5f2X/dYWAJvwMPB1lQ0DEv9S8QJelYWVjN1OF Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2586 Archived-At: All, On Fri, May 03, 2019 at 02:53:21AM +0200, Jeff wrote: > what init systems do this list's subscribers use ? I saw Guillermo's reply up-thread, so I thought I'd add my own two cents. My main workstation at present is a Debian 9 box booted with s6 and s6-rc, with system setup and teardown (i.e. stages 1 and 3) handled by some execline scripts heavily adapted from those generated by s6-linux-init-maker 0.4.x.x. It's been nearly two years since I set this up, so I don't recall all the details, but I started out with a sysvinit Debian 9 system, and reverse-engineered the boot sequence, which included a by-hand conversion of all the necessary /etc/init.d scripts into s6-rc service definitions. The boot process follows the general flow to be expected from a system using s6-svscan as PID 1. The stage 1 script sets up an initial service directory, spawns the script which starts stage 2 and then exec's into s6-svscan. Most of the runtime state configuration and management is then handled through s6-rc in stage 2. Stage 3 involves deactivating all the s6-rc managed services and then signalling the PID 1 s6-svscan, which execs into a script which kills the remaining processes, unmounts filesystems and then performs a halt, poweroff, or reboot as necessary. The particulars of the configuration I'm using are generally not portable to other machines though, as it was a proof-of-concept I came up with a year or two or go for a different system, which I then ported to my current workstation, which was set up in a very similar manner. I've also had to make it largely signal-compatible with sysvinit, as apt(8) sometimes attempts to reload the init configuration upon package changes. The signal used to request a configuration reload from sysvinit is SIGUSR1 if I recall correctly, however the default behaviour of the version of s6-linux-init-maker I was using at the time was to power off the machine upon receiving SIGUSR1 in PID 1, so I had to change the signal configuration for s6-svscan. That being said, it's been very stable and has largely stayed out my way, so it's been worth the initial setup effort in the long run. Cheers, --multiplexd.