On Fri, 14 Jul 2017 22:29:04 +0300 Jean Louis <bugs@gnu.support> wrote:
> On Fri, Jul 14, 2017 at 02:31:28PM -0400, Steve Litt wrote: > > > If you're fine with it not being supervised and insist on > > > launching s6-svscanboot from /etc/rc.local, then you want to > > > enclose all its commands in a "background { }" block, which is > > > execline's equivalent of the shell's &. > > > > Or, from sysvinit, you can put it as a respawn in /etc/inittab, so > > that s6svscanboot itself is supervised, by sysvinit. > > On that new Debian VPS that I ordered with Digital > Ocean, there is no /etc/inittab and I don't know > nothing much about systemd, so I just used recipe > from stackexchange.com So you can either do it like you are now, and if s6svscanboot goes down your whole supervision tree goes down and stays down, or you can make a systemd unit file for s6 and run it from there, and if s6-svscanboot goes down it will come right back up. You can probably experiment at home with a Debian virtual machine host to get just the right unit file and how to tell it to run itself. SteveT Steve Litt July 2017 featured book: Quit Joblessness: Start Your Own Business http://www.troubleshooters.com/startbiz