Others have touched on the major points, but the two that have burned me:
Needlessly obtuse binary logging format, and difficult-to-read output from the tools to access the logging facility. Very often you’ll have a service start failure, run ‘journalctl -xe’ or whatever it recommends, and get a half screen of crap that doesn’t even include the program’s output.
Bad defaults for many use cases (e.g. terminating your tmux/screen session after logging out of SSH, thanks for letting that one through, Debian)
The person/people (who will not be named) who wrote it will (semi-justifiably) pass the buck to the project managers.
It’s really easy to write it off as a “let’s make Linux more like Windows” thing, but it does have a decent set of features now. The justifications for hatred for it have waned in my mind, though I admit I don’t have to interact with it from day to day. It does, however, remain somewhat annoying.
edit: also, my usual (if available) solution for log-eating is to just have the things I care about send to my main computer’s syslog server and forget about it. I’ll do my own log centralization, thanks.
Latest Answers