On Sep 13, 2014, at 9:47 AM, Balint Szigeti <balint.szgt@xxxxxxxxx> wrote:
I don't understand the problem. You're saying logs are found in journalctl and messages, so what's the bug/problem? systemd-journald is expected to always run because it knows a ton of what's going from the kernel and systemd itself. The traditional syslog needs to be systemd-journald compatible, and I'm pretty sure rsyslog is. It directly reads the stream from systemd-journald. http://www.freedesktop.org/wiki/Software/systemd/syslog/ http://blog.delouw.ch/2013/07/24/why-journalctl-is-cool-and-syslog-will-survive-for-another-decade/ If you merely delete /var/log/journal, then systemd-journald will log to /run/log/journal which is not persistent. And a journald compatible syslogger will read that stream, and log it to /var/log/messages just like before except it probably contains more information since it should contain all journald logged events before syslogd started. I don't think none is what you want because then syslog has nothing available to it to log. At least that's my understanding of it. Chris Murphy |
-- 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
