Redhat's M.O. seems to be "we need to improve this part of the ecosystem"
Then they toss it into the RHEL meat grinder at camp Poettering and out comes something that might be better but nobody will ever know because it's impossible to understand.
Oh and "Make sure the configuration is in some stupid fucking markup language for no obvious benefit, and it must interact with DBUS in some really weird way"
@ParadeGrotesque We put linux in some cars so if you like text logs you can go and fuck yourself
@ParadeGrotesque "The Fedora devs don't look at logs so we thought nobody else should, either."
You mean, you look at logs to analyze a problem? How quaint!
Just use systemd-issuesd like normal people do, you weirdo!
Does not work on your system? Go back to BSD or Slackware or get on with the program!
@ParadeGrotesque Everybody uses a web server and QR code to look at logs nowadays!
Web server and QR codes? Nah, just use systemd-curl [please note: not real curl, the systemd replacement, of course] to query the error message from the system API!
Make sure systemd-webinfod is activated and systemd-firewalld is deactivated first. Of course.
Also: pleae note that, once systemd-apireportd is activated YOU CANNOT EVER REMOVE IT. 🤓
@ParadeGrotesque Hahah, indeed. What a mess.
@sullybiker
And don't forget: the logs must not be human-readable anymore, because why look at logs? Why, indeed?