On Fri, Jul 14, 2017 at 05:51:01PM -0400, Steve Litt wrote: > 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.
As for me is just important to run 3 http daemons under Nginx, now I made it simpler, after recommendations from this list, I have /etc/systemd/system/s6.service: [Unit] Description=S6 Supervision ConditionPathExists=/service [Service] Type=forking ExecStart=/command/s6-svscan /service TimeoutSec=0 StandardOutput=tty RemainAfterExit=yes SysVStartPriority=99 [Install] WantedBy=multi-user.target and if I write: service s6 start (after stop), I can see I am still bound to console, which is for me as user not so clear why. For example nginx releases me back to console. But I press C-c and daemons are running. On reboot everything is fine and running too. Jean