Bug in yum Logwatch reporting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



I've been noticing yum updates on several servers I manage over the
last few weeks, which I know I didn't perform and could not explain
until this morning.  At first I suspect a break-in, but found no other
evidence or reason an intruder would run the yum updates I was
viewing.

Yum updates are logged in /var/log/yum.log, which is what Logwatch
scans.  Seems that the format of the log entries is: "MMM DD", the
year is missing!   This morning looking at this log sequentially I
noticed I did do yum updates on Apr 02 and Apr 03 as reported in last
night's logwatch, but not April of 2009, but rather April of 2008!

Has anyone else noticed this behavior and/or know if there is a fix in
progress for it?

Brett
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos

[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux