On March 6, 2015 17:37:41 Michael Biebl wrote: > Can you check the status of syslog.socket (systemctl status > syslog.socket), it should not be active. > The journald -> syslog forwarding is also explicitly disabled in > fedora via /etc/systemd/journald.conf, see ForwardToSyslog=no
I've got #ForwardToSyslog=yes and the journald.conf man page claims that yes is the default. I haven't ran "yum update" in a bit though, so I may be looking at the old Fedora 20 defaults. Maybe my issue is that I really needed to update my systemd stuff to the latest when I installed the rsyslog package. Possibly this could explain the strange syslog.socket symlink thing I saw earlier too. Thanks! -Tyson _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
