Poettering: Revisiting how we put together Linux systems

Posted Sep 4, 2014 23:46 UTC (Thu) by flussence (guest, #85566)
In reply to: Poettering: Revisiting how we put together Linux systems by jackb
Parent article: Poettering: Revisiting how we put together Linux systems

> Except in my case, I really just want the feature of automatically restarting crashed daemons, and automatically funnelling all their console output into the journal.

I've found runit handles both those things flawlessly. Half of my system daemons are running under it — the other half's still on OpenRC, but that's mostly due to laziness.

Poettering: Revisiting how we put together Linux systems

Posted Sep 5, 2014 8:50 UTC (Fri) by cortana (subscriber, #24596) [Link] (4 responses)

Runit fails to deal with daemons that themselves fork and manage their own children.

Poettering: Revisiting how we put together Linux systems

Posted Sep 6, 2014 0:21 UTC (Sat) by flussence (guest, #85566) [Link] (3 responses)

That's true, but I've yet to encounter anything that misbehaves in that way. If and when that happens I'll be sure to complain upstream.

Poettering: Revisiting how we put together Linux systems

Posted Sep 6, 2014 0:47 UTC (Sat) by Cyberax (✭ supporter ✭, #52523) [Link]

A Python daemon using the multiprocessing module. Yes, I've seen it personally.

Poettering: Revisiting how we put together Linux systems

Posted Sep 6, 2014 9:38 UTC (Sat) by cortana (subscriber, #24596) [Link]

Jenkins and pretty much anything else written in Java.

Poettering: Revisiting how we put together Linux systems

Posted Sep 6, 2014 15:45 UTC (Sat) by rahulsundaram (subscriber, #21946) [Link]

Complaining about this is pointless unless the upstream you are referring to, is the init system itself. There is a ton of software out there that does it. If your init system cannot handle it, it is a failure of the init system.