On Tue, 23 Feb 2016 13:55:08 + Richard Harris
wrote:
> There is no need to guess, you can run logrotate with the --verbose setting
> and find out which log it was processing before the error occured. A good
> way to do this is to modify the logrotate cron to add --verbose and sit and
> wait fo
On Wed, 17 Jun 2015 11:44:02 +1200 Alex King wrote:
> I suspect the message will be from a configuration which includes the
> compress option without. delaycompress.
There is no need to guess, you can run logrotate with the --verbose setting
and find out which log it was processing before the err
I'd also like to see this bug fixed, and #786757 which is a similar
problem.
In the mean time, as a workaround, the following might help people
diagnose the problem:
I suspect the message will be from a configuration which includes the
compress option without. delaycompress. So:
cd /etc/
3 matches
Mail list logo
