From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: reversion of access.log commenting out in rootfile
Date: Fri, 09 Aug 2024 17:25:21 +0200
Message-ID: <ffbb9e49-2e49-489b-aa4c-1abee0652ee0@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8783799220683026421=="
List-Id: <development.lists.ipfire.org>

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

Hi Arne,

I saw that my patch for commenting out the access.log in the rootfile had bee=
n reverted.

https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3D97067db7862450bb40d=
4e9188627d6b5585bf931

I don't understand the meaning of

"the file was created to be shipped with permissions
so it is needed in the rootfile."

If it has to stay how do we ensure that users don't lose maybe up to a weeks =
worth of the access.log file if an update is done on the day before access.lo=
g would be rotated to access.log.1 .gz

Although this has always been the case, it doesn't seem right to overwrite th=
e existing access.log file if squid is updated or have I misunderstood someth=
ing?

Regards,

Adolf.


--===============8783799220683026421==--