Re: Logwatch (randomly) skipping days => Feature!?

[Tom Rymes <trymes@rymes.com>]

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

Is this a ticking issue where one log has two days’ data and the other is empty?

> On Feb 17, 2019, at 4:22 AM, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> I discovered something weird:
> 
> From time to time 'logwatch' does not create a daily log.
> 
> E.g.:
> The file '/var/log/logwatch/2019-14-26' exists, but size = 0 Bytes.
> 
> The same happened yesterday with '/var/log/logwatch/2019-02-16':
> 0 Bytes.
> 
> After running...
> 
> /usr/local/bin/logwatch > /var/log/logwatch/`date -I -d yesterday`; \
> LOGWATCH_KEEP=$(sed -ne 's/^LOGWATCH_KEEP=\([0-9]\+\)$/\1/p'
> /var/ipfire/logging/settings); \
> find /var/log/logwatch/ -ctime +${LOGWATCH_KEEP=56} -exec rm -f '{}' ';'
> 
> ...manually from console, file was created, everything looks ok.
> 
> 1. Can anyone confirm?
> 
> 2. With which parameter could I change the starting time "01 0 * * *" so
> that this doesn't happen again? I'm searching, but can't find a grip on
> this...
> 
> Best,
> Matthias