4 ms·
These "simple" use cases break when you need to do anything even slightly more complex than whatever the systemD designers envisioned for the user. And if you
by zozbot234 4y ago
These "simple" use cases break when you need to do anything even slightly more complex than whatever the systemD designers envisioned for the user. And if you try to submit an issue upstream, the typical response is "you're holding it wrong" or equivalent. This lack of a consistent design might be excusable when first trying to support a bunch of entirely novel use cases, but let's not pretend that it doesn't come with serious drawbacks.
- sophacles 4y agoI have yet to encounter something that systemd doesn't do OK or well. What is your example of something that systemd can't handle that was better handled by init scripts?
- ElectricalUnion 4y agoThese "simple" use cases break when you need to do anything even slightly more complex than whatever the sysvinit scripts you copied envisioned. FTFY systemd might be sad but makes the simple case simple. sysvinit makes everything complex and error prone.
- sam_lowry_ 4y agosysvinit could be debugged, at least. I tried to debug a couple of systemd edge cases with Pottering, communicating over Github Issues, but he lost interest very quickly. To his, credit he is reactive until he decides the issue is not worth his time. To his discredit, he made himself into a giant bottleneck. Random systemd users can not easily understand it.
- kaba0 4y agoI’m sure then you can list a use-case which doesn’t work under systemd. Please do so, otherwise you are not contributing much.