Poettering: The Biggest Myths
Posted Jan 31, 2013 23:35 UTC (Thu) by khim
In reply to: Poettering: The Biggest Myths
Parent article: Poettering: The Biggest Myths
Since systemd doesn't invent the way to do this (it uses cgroups provided by the kernel), why not just create a service launcher command that creates the cgroups as needed instead of taking over everything else that systemd does?
You assume I know in advance which service will start misbehaving. And I don't. Sure, I have some suspects but in reality all of them can misbehave (I've seed many pretty innocuous services turning to fork bombs because of configuration mistakes). And if you run all your services using such launcher then why do you need to keep useless sysvinit baggage in PID1?
P.S. Cron scripts are especially problematic - that's why I like the fact that systemd offers timer units to replace them.
to post comments)