The Pain of systemD...

...experienced up-close-and-personal. I've only heard bad things about it, but this is the first time I got poettered¹ trying to troubleshoot something on a customer's system. It turns out others are complaining about it too:

https://utcc.utoronto.ca/~cks/space/blog/linux/SystemdSensibleOutput
https://github.com/systemd/systemd/issues/3617
https://bugzilla.redhat.com/show_bug.cgi?id=713567

Some fuckface decided that truncating the output and hiding useful information, adding extra code to deliberately do that and invoke an external program, was somehow "better" than just writing the full output and letting the terminal/pipeline/etc. handle the rest. I'll pipe the output if I need to. WHAT THE FUCK!?!?!

¹ poetter; poettering; poettered: a gigantic fuck-up.

>>13

and revert back to using SysVInit?

I think there should be a new more modern initsystem with little to no feature creep.
That's not to say SysVInit is bad, but it's just that you can't go forward if you stick to the same old thing for decades. SystemD is aids, however.