Re: Bug#727708: Fsck SystemD and its developers and its users. GR to override this please.
Because it's work, for no apparent gain. I mean, the systemd people
just code up all that journal stuff for no good reason, but because
perceived a need to have it. And let's face it, the ability to just see
stderr output from $FAILED_JOB with "systemctl status" is a whole damn
better than to restart the thing in the foreground and hope to be able
reproduce the problem that caused it to die.
You can split off systemd-journal and its supporting files into a
binary package. That'd probably be quite simple. The question is, why
you even want to ..?
Because I want logs to be plaintext in my system, not binary.
And I don't see why a binary log format is needed to implement the
With best regards,