On Sun, 15 Jan 2017 13:58:30 -0800 39066...@gmail.com wrote: > On Sun, Jan 15, 2017 at 12:28:49PM -0500, Steve Litt wrote: > > > That sounds sensible on a desktop. In my case the motivation is to > > > trim a source of power draw for an image that's going to run on a > > > battery-powered device that will be awake but idle a lot of the > > > time. Why Linux? Pretty much familiarity & tooling, if power is > > > ok then I get to have my cake and eat it too. > > > > Why not try s6? IIRC, s6 doesn't poll, is a little more complex than > > runit, but like runit, it's a daemontools descendent. I've used it > > and like it.
[snip] > > I used s6 on a project last year and did like it. For this I'm using > a distro (Void) that comes with runit as the standard init, switching > would entail changes for third party services. Not all that bad but > I'd like to avoid it if I can. I use Void and runit every day and am thankful for it. On switching to s6: Both runit and s6 inherited a lot of their API from djb's daemontools. They're similar enough that switching would be trivial, and perhaps even automated. After I wrote and publicized http://troubleshooters.com/linux/diy/suckless_init_on_plop.htm , which describes a Felker or Felkeristic PID1 combined with a daemontools-encore supervision system, Laurent Bercot asked me why I hadn't used s6 instead, so I switched it over to s6, and it worked perfectly. It really wasn't much work to make the switch. If you have a bad feeling about polling, s6 might be your kind of supervisor. I have a feeling you could use runit's PID1 with the s6 supervisor, although I don't know for sure. Or, use s6 as both PID1 and supervisor. Or use s6 plus s6-rc. SteveT Steve Litt January 2017 featured book: Troubleshooting: Just the Facts http://www.troubleshooters.com/tjust