> 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.
? You end up diving in to the service file vs. the script.
> And don't get me started on binary log files.
Having worked with binary and plaintext log data for the better part of a decade now, I have to say that pretty much the entire set of claimed advantages of plaintext log data is very wrong, and we've wasted a ton of productivity & efficiency because of it.
If you really are sure of its superiority though, just put a little stub in front that converts the binary log to a human readable format that still needs a program in order to present to the user...
> SysVInit has served me thus far with no issues.
Speaking of attitude... there are two ways to look at that datapoint...
? You end up diving in to the service file vs. the script.
> And don't get me started on binary log files.
Having worked with binary and plaintext log data for the better part of a decade now, I have to say that pretty much the entire set of claimed advantages of plaintext log data is very wrong, and we've wasted a ton of productivity & efficiency because of it.
If you really are sure of its superiority though, just put a little stub in front that converts the binary log to a human readable format that still needs a program in order to present to the user...
> SysVInit has served me thus far with no issues.
Speaking of attitude... there are two ways to look at that datapoint...