I think I found it...and I think it is a bug.
Here is a file in usr/share/logwatch/default.conf/logfiles/cron.conf
It appears this file tells it where to look for the cron file...and the cron
file location is dead wrong.
It should be /var/log/cron I believe.
Is this the correct fix to make logwatch once again grab my cron files since
5.5 update?
##########################################################################
# $Id: cron.conf,v 1.11 2005/02/24 17:05:18 kirk Exp $
##########################################################################
########################################################
# This was written and is maintained by:
# Kirk Bauer <kirk@xxxxxxxxxx>
#
# Please send all comments, suggestions, bug reports,
# etc, to kirk@xxxxxxxxxxx
########################################################
# What actual file? Defaults to LogPath if not absolute path....
#Solaris is /var/cron/log -mgt
LogFile = /var/cron/log
LogFile = cron
# If the archives are searched, here is one or more line
# (optionally containing wildcards) that tell where they are...
Archive = cron.*
Archive = archiv/cron.*
*OnlyHost
*RemoveService = anacron
# vi: shiftwidth=3 tabstop=3 et
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
