On Sat, 2014-07-05 at 20:15 -0600, Kevin Fenzi wrote: > On Sat, 5 Jul 2014 22:10:40 -0400 > Tom Horsley <horsley1...@gmail.com> wrote: > > > On Sat, 5 Jul 2014 19:56:09 -0600 > > Kevin Fenzi wrote: > > > > > With systemd/journald, ALL output is saved and easy to query. > > > > With journald all output is saved in a binary format file that > > (which is fully documented) > > > is impossible to query when examining a crashed system because > > is is always corrupted (especially when there are systemd > > bugs causing the crash). 9 times out of 10, you won't be able to > > boot the system again unless you remove the corrupted > > journal file (and it only takes a couple of days of searching > > to discover that is the problem :-). > > Sorry to hear you ran into this. > > I've run into one journald bug like that last year sometime in > rawhide... but it was pretty quickly fixed and there was a workaround > the same day I think. > > kevin
but is it impossible to configure systemd to save logfile into text files instead of journal file? or we should have syslog service (i.e. rsyslog) for this balint
-- users mailing list users@lists.fedoraproject.org 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
