Systemd Sucks, Long Live Systemd

Post by kasabali » Mon, Jan 16, 2017, 5:20 PM UTC

Yet another systemd post which

- Handwaves real criticisms and instead tries to look like an objective writing by presenting a trivial issue

- Have no idea about advances in sysvinit in the last decade that allowed support for parallel boot and dependency relations (and which was supported natively on mainstream distribution)

- Totally ignores the other "modern" and widely used init system and instead compares systemd with sysvinit of 80's (which wasn't used by any mainstream distro in that form)

- Overrates process supervision features which were already as equally as easy to use with supervision suites like runit (IMHO even easier)

Meh, what did I expect? Bandwagon is going full speed.

Post by kasabali » Mon, Jan 16, 2017, 5:27 PM UTC

kinghajj wrote: post #81

plorg wrote: post #76

Earlier quoted context omitted.

As a single user with a number of personal/hobbyist machines, I actually find systemd annoying to work with for precisely this reason. If a daemon is misconfigured and fails to launch several times in a row, it inevitably triggers the systemd "too many retries" error, after which systemd will refuse to start the daemon until some timeout has expired or the counter is cleared. This makes troubleshooting more difficult…

Funnily enough, just dealt with a bug caused by this at work. The small PC would boot before the cellular modem had an Internet connection. Services that communicate via MQTT would immediately attempt to reach the broker, and throw an exception. My quick fix was just to add "RestartSec=5" so that the faulted state would never be entered.

Ironic considering how systemd developers brag about eliminating race conditions and sleep calls from init scripts.

Re: Systemd Sucks, Long Live Systemd

Re: Systemd Sucks, Long Live Systemd