[byte_0]

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.

[rcxdude]

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).

[ptx]

> the thing you were running was generally expected to do the double-fork hack itself and otherwise do 'well behaved daemon' things

FreeBSD has a general utility that does this for you, daemon(8): https://man.freebsd.org/cgi/man.cgi?query=daemon&sektion=8

[bandrami]

Is this really that hard to type?

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

[IshKebab]

Yes, much better. The original intro blog post goes into detail: https://0pointer.de/blog/projects/systemd.html

[0xbadcafebee]

One is not better than the other because they exist to solve different problems. Are sandals technically better than snowshoes?