devil-linux-discuss

[Devil-Linux-discuss] cron.daily errors with 1.3.4

[Dick M. <di...@fo...>]

Since moving to 1.3.4 I've been getting messages like this every day:

Cron <root@Devil> /usr/sbin/cron.interval daily

zcat: /var/log/mail.log.4.gz already has .gz suffix -- unchanged
zcat: /var/log/mail.log.3.gz already has .gz suffix -- unchanged
zcat: /var/log/mail.log.2.gz already has .gz suffix -- unchanged
zcat: /var/log/messages.2.gz already has .gz suffix -- unchanged
zcat: /var/log/apache2/access.log.2.gz already has .gz suffix -- unchanged

It seems to be logwatch that is producing these.

Anybody else seeing this?

Dick

Re: [Devil-Linux-discuss] cron.daily errors with 1.3.4

[Dick M. <di...@fo...>]

Dick Middleton wrote:
> Since moving to 1.3.4 I've been getting messages like this every day:
> 
> Cron <root@Devil> /usr/sbin/cron.interval daily
> 
> zcat: /var/log/mail.log.4.gz already has .gz suffix -- unchanged
> zcat: /var/log/mail.log.3.gz already has .gz suffix -- unchanged
> zcat: /var/log/mail.log.2.gz already has .gz suffix -- unchanged
> zcat: /var/log/messages.2.gz already has .gz suffix -- unchanged
> zcat: /var/log/apache2/access.log.2.gz already has .gz suffix -- unchanged
> 
> It seems to be logwatch that is producing these.

I think this is because zcat is a sym link to gzip

On Debian zcat is a script which does exec gzip -cd "$@"

So here zcat is trying to compress file again rather than uncompress and send to 
stdout.

Dick