This problem still exists in 3.7-5:
-rw-r--r-- 1 root root 8303 Aug 28 13:47 cron.log.2.gz
-rw-r--r-- 1 root root 7677 Aug 28 13:39 cron.log.1
-rw-r--r-- 1 root root 8416 Aug 28 06:33 cron.log.3.gz
which seems strange, as gzip doesn't normally alter the timestamp, as
documented:
gzip preserves the mode, ownership and timestamps of files when
compressing or decompressing.
That would suggest logrotate is doing something more than just renaming
and compressing the old logs.
This problem is probably only noticeable if the 'delaycompress'
directive is used.
-Tom
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
