Earlier quoted context omitted.
And if that service file screws up how do you troubleshoot it? You end up diving in to the source code of systemd, versus fixing a bug in your script. And don't get me started on binary log files. As was said before, buster, your attitude is the problem. It's the same as the systemd developers and those within the community. SysVInit has served me thus far with no issues.
And if that service file screws up how do you troubleshoot it? You end up diving in to the source code of systemd, versus fixing a bug in your script. That's a good thing, because if you find a bug, it will be fixed for everybody, not just for your one-off init script. your attitude is the problem The attitude here is to fix problems at their source. Instead of using the hammer for everything, sometimes coming up wit…
Generally I agree with this at a broad level. But, there is still the problem of: I need this running now. To do that, I need to compile and run a custom systemd, and hope that my patch gets accepted upstream, and that in a few months my distro finally adopts it and puts it in the standard package.
Generally speaking I really like systemd and am excited to get some time to update my installed stuff to use it, but the above is a real concern.