From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: Re: Logwatch (randomly) skipping days => Feature!?
Date: Sun, 17 Feb 2019 09:42:45 -0500
Message-ID: <69823681-C00C-4FF2-8D6E-22F88ED93664@rymes.com>
In-Reply-To: <acb1c40b-835b-3584-dfea-d7a48ae06d84@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2061170804805357017=="
List-Id: <development.lists.ipfire.org>

--===============2061170804805357017==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Is this a ticking issue where one log has two days=E2=80=99 data and the othe=
r is empty?

> On Feb 17, 2019, at 4:22 AM, Matthias Fischer <matthias.fischer(a)ipfire.or=
g> wrote:
>=20
> Hi,
>=20
> I discovered something weird:
>=20
> From time to time 'logwatch' does not create a daily log.
>=20
> E.g.:
> The file '/var/log/logwatch/2019-14-26' exists, but size =3D 0 Bytes.
>=20
> The same happened yesterday with '/var/log/logwatch/2019-02-16':
> 0 Bytes.
>=20
> After running...
>=20
> /usr/local/bin/logwatch > /var/log/logwatch/`date -I -d yesterday`; \
> LOGWATCH_KEEP=3D$(sed -ne 's/^LOGWATCH_KEEP=3D\([0-9]\+\)$/\1/p'
> /var/ipfire/logging/settings); \
> find /var/log/logwatch/ -ctime +${LOGWATCH_KEEP=3D56} -exec rm -f '{}' ';'
>=20
> ...manually from console, file was created, everything looks ok.
>=20
> 1. Can anyone confirm?
>=20
> 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...
>=20
> Best,
> Matthias

--===============2061170804805357017==--