zlacker

[return to "Linux From Scratch ends SysVinit support"]
1. byte_0+Zh[view] [source] 2026-02-02 19:12:36
>>cf100c+(OP)
From a completely technical standpoint, is systemd really better than SysVInit? I ask this question in good faith. I have used both and had no problems with either, although for personal preference, I am more traditional and favor SysVInit.
◧◩
2. rcxdud+fj[view] [source] 2026-02-02 19:20:18
>>byte_0+Zh
I always dreaded trying to create a service with bash-based init scripts. Not only did it involve rolling a heck of a lot yourself (the thing you were running was generally expected to do the double-fork hack itself and otherwise do 'well behaved daemon' things), it varied significantly from distro to distro, and I was never confident I actually got it right (and indeed, I often saw cases where it had most definitely gone wrong). Whereas systemd has a pretty trivial interface for running most anything and having some confidence it'll actually work right (in part because it can actually enforce things, like actually killing every process that's part of a service instead of kind of hoping that killing whats in the PIDfile is sufficient).
◧◩◪
3. bandra+o02[view] [source] 2026-02-03 04:33:20
>>rcxdud+fj
Is this really that hard to type?

https://github.com/openbsd/src/blob/master/etc/rc.d/watchdog...

◧◩◪◨
4. abenga+Ns2[view] [source] 2026-02-03 08:44:17
>>bandra+o02
Probably not, but it looks a hell of a lot harder to understand than a unit file.
◧◩◪◨⬒
5. bandra+lx2[view] [source] 2026-02-03 09:18:35
>>abenga+Ns2
Huh? Not even remotely
◧◩◪◨⬒⬓
6. abenga+2O3[view] [source] 2026-02-03 16:49:55
>>bandra+lx2
It's probably straightforward for someone who works with it. For a newb like me, it needs effort to understand. I think unit files are self-documenting and straightforward to understand the first time you see them.
[go to top]