https://bugzilla.novell.com/show_bug.cgi?id=809852 https://bugzilla.novell.com/show_bug.cgi?id=809852#c16 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #16 from Marius Tomaschewski <mt@suse.com> 2013-05-27 10:21:07 UTC --- (In reply to comment #15)
# zypper se -i -s libestr rsyslog
S | Name | Type | Version | Arch | Repository --+----------+---------+-------------+--------+--------------------- i | libestr0 | package | 0.1.5-2.4.1 | x86_64 | openSUSE-12.3-Update i | rsyslog | package | 7.2.7-2.5.1 | x86_64 | openSUSE-12.3-Update
I noticed, that after restarting rsyslog without any changes to the config, the cron messages now end up in /var/log/messages, instead of /var/log/dhcp.log. They also still go into /var/log/cron.log
I think I know what you mean. There are e.g. pam messages like: /usr/sbin/cron[13588]: pam_unix(crond:session): session opened for user root by (uid=0) /USR/SBIN/CRON[13588]: pam_unix(crond:session): session closed for user root which look like cron messages, but they aren't. Your filter is cron.*, that is factility "cron" (9), level any. Look into the journal using: journalctl -o export | less and search for the messages of interest, you'll find out, that it were not logged with the "cron" facility "SYSLOG_FACILITY=9", but with "authpriv" "SYSLOG_FACILITY=10" (in above example). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.