On Wed, May 06, 2015 at 09:30:35AM +0200, Jon Ingason wrote: > Den 2015-05-06 08:55, franta@xxxxxxxxxxx skrev: > >> ... Other parts are > >> actually really cool, like management of services throughout their > >> whole lifetime, relevant log messages automatically shown for > >> "systemctl status", > > > > I am personally convinced that journalctl and its binary logs are one of > > the big systemd mistakes. And that grep/awk/sed/... over classical text > > logs always will be more poverfull than systemd journal stuff. > > > You can still use "grep/awk/sed/..." :-) That is a deceptive similarity. I find journalctl output too verbose at times. Also it can just be a lot in terms of quantity (how far back the logs go). Under such circumstances, using the "old" methods can be bit of a chore. One would then say filter the output of journalctl (or rotate the journal)! But the documentation for that is in such a terrible state, as in very hard to comprehend for someone not familiar with internal details, it's almost funny. See this message for a rather egregious example: http://thread.gmane.org/gmane.linux.redhat.fedora.general/440292/focus=440647 The rest of the thread is also very instructive. One of these days if I find some time, I'll file a bug report for documentation. But if someone else wants to, please go ahead. Cheers, -- Suvayu Open source is the future. It sets us free. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
