Post #2400888
2026-05-07 07:33 UTC
@benjamineskola@hachyderm.io for sure. It's just not great at handling independent, blocking tasks that need to do things in a very specific order. While there are some controls, the default behavior (and dare I say design philosophy) of systemd is "runlevel N reached: do all of its tasks at the same time!" Great if you're running a laptop or whatever braindead container format is fashionable this week, tricky at best if you're running a complex server.
Replies (2)
-
@me@social.taupehat.com 2026-05-07 07:34
@benjamineskola@hachyderm.io so, we're back to individual scripts that run in numerical order, each blocking until it's done.
-
@benjamineskola@hachyderm.io 2026-05-07 07:36
@me@social.taupehat.com Right, yeah, if it’s a specific ordering you need then presumably it’s better to just have one unit running a command that runs all the other things sequentially, as you say. (Or presumably you could also define them all as separate units and specify the real dependencies in each unit, but maybe not worth the effort.) Must admit I haven’t had this issue precisely because I only run systemd on a laptop; my servers run FreeBSD.