"alternative to the classic BSD syslog protocol for locally delivering log records to the Journal,"
I was about to say I'm very slowly coming to accept systemd (note that's accept, not like) but the main thing that really infuriates me still is the need to use a completely separate util/command just to see what systemd is logging (or spewing) so I can try and actually figure out why a service won't start. As just telling me the error/output when the actual command is run is obviously far too useful/intuitive.
If ever there was a case making something more user-unfriendly or making it so much more complicated than it needs to be... this is a prime example.
Biting the hand that feeds IT
