If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

First thing that came to mind: Does this exclusively happen with these cron logs, or other files as well.

If cron exclusively, how is cron configured?

from cron man page ( FC3 )

SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log
file. This is useful in scripts which rotate and age log files. Nat-
urally this is not relevant if cron was built to use syslog(3).

Could something like this be happening? Or am I way off base?

" And maddest of all, to see life as it is and not as it should be" --Miguel Cervantes

The listed date is the date is was last used. During each rotation the name is changed ( the larger the extension, the older the file ) , but not the date. So in the above example, maillog is currently in use, maillog.1 was last used last Sunday Dec 4 when the log rotated, maillog.2 was last used the Sunday before that ( Nov 28 ), but at that time was named maillog.1, renamed to maillog.2 this past Sunday, etc.

Since he didn't include a date, I assumed ( silly me ) that this wasn't an issue. But it may very well be what he is looking at.

" And maddest of all, to see life as it is and not as it should be" --Miguel Cervantes