Even for basic service running, complex dependencies are so much more manageable in systemd.
I'm glad systemd "won"; it's much more maintainable IMO than shell scripts written once and forgotten about (until they break).
I'm glad systemd "won"; it's much more maintainable IMO than shell scripts written once and forgotten about (until they break).
With one exception... I tried to set up a inetd-like service where a script was run on TCP connection with the output going out to the socket. It was tricky to get set up, but eventually I got it working... or so I thought. A few days later the system was super sluggish and I found that every connection that had been made to this service was left open and consuming resources. Switched that to an socat running under systemd and it's been fine since. Never could figure out what exactly the deal was.