On Jan 1, 2014, at 7:39 PM, Suvayu Ali <fatkasuvayu+li...@gmail.com> wrote:
> > More to the point, I find it counter productive to _remove_ important > debugging resources/tools irrespective of the technical proficiency of > the user of the system. I switched to journalctl when it first appeared as non-persistent logging, by creating /var/log/journal to make it persistent, and disabled rsyslog. I'm not a particularly technical user, I prefer the parsing options in the journal rather than having to look at different files or even different commands. rsyslog uses the same journal file journalctl does. The only difference is some differences in the formatting. The same exact information is available with both, although you'll find rsyslog drop some things it doesn't care about that will be in journalctl. The other thing is that the journal is available straight way, even if you get dropped to a dracut shell. It's available way sooner than rsyslog was, and the journal is integral to systemctl status messages. So it's simply a better debugging tool. But if you like messages output better, you're exactly one command from installing it. I don't see what the big deal is. > I outlined my issue in this post: > > <https://lists.fedoraproject.org/pipermail/users/2013-December/444436.html> > > Anyone care to comment on this? > I'm a regular user. I don't use rsyslog's /var/log/message, I disable it always for some number of releases now. Chris Murphy -- 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
