http://bugzilla.novell.com/show_bug.cgi?id=991190 http://bugzilla.novell.com/show_bug.cgi?id=991190#c3 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #3 from Jiri Slaby <jslaby@suse.com> --- (In reply to Dr. Werner Fink from comment #1)
man:systemd-journald(8)
/dev/kmsg, /dev/log, /run/systemd/journal/dev-log, /run/systemd/journal/socket, /run/systemd/journal/stdout Sockets and other paths that systemd-journald will listen on that are visible in the file system. In addition to these, journald can listen for audit events using netlink.
I don't care about paths journald listens on at all. man:journald.conf(5) FORWARDING TO TRADITIONAL SYSLOG DAEMONS Journal events can be transferred to a different logging daemon in two different ways. With the first method, messages are immediately forwarded to a socket (/run/systemd/journal/syslog), where the traditional syslog daemon can read them. This method is controlled by the ForwardToSyslog= option. (In reply to Dr. Werner Fink from comment #2)
Btw: After rsyslog here and enabling ForwardToConsole=yes in /etc/systemd/journald.conf and rebooting the system I see
I haven't tried to reboot, I only restarted the service which should be enough IMO. -- You are receiving this mail because: You are on the CC list for the bug.