From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: reversion of access.log commenting out in rootfile
Date: Tue, 13 Aug 2024 13:04:51 +0200 [thread overview]
Message-ID: <0a558cdd-3241-4ca1-a388-2b6d0024f108@ipfire.org> (raw)
In-Reply-To: <F5FC5FD2-1699-46E7-8F5B-8F1062C20896@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2085 bytes --]
Hi Michael & Arne,
On 13/08/2024 11:57, Michael Tremer wrote:
> Hello,
>
> I am going to reply on Arne’s behalf...
>
>> On 9 Aug 2024, at 16:25, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Arne,
>>
>> I saw that my patch for commenting out the access.log in the rootfile had been reverted.
>>
>> https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=97067db7862450bb40d4e9188627d6b5585bf931
>>
>> I don't understand the meaning of
>>
>> "the file was created to be shipped with permissions
>> so it is needed in the rootfile."
>
> The file is created with other than default ownership than root or maybe other permissions than 644.
I will need to have a sit-down and think further on understanding this.
However, I believe it when you say that it causes a problem if it is
removed from the rootfile.
>
> There is a follow-up commit which should exclude it from being overwritten:
>
> https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=6f83ae4c959045c866c08cc326f36ff645952ae4
I hadn't seen that commit. Looking at it, that should solve the issue.
>
> Can you confirm that this works, too?
I was able to test this.
I looked in my Proxy Logs via the WUI for when I ran the CU186 update
and the four days before that date my proxy log was empty.
I then looked in the proxy logs for the days before CU187 was run. I
updated CU187 the day before the access logs would have been rotated so
nearly a week would have been lost.
I can confirm that the access.log is fully present for the whole week
before CU187 was updated so the commit worked perfectly.
Regards,
Adolf.
>
>>
>> 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.log would be rotated to access.log.1 .gz
>>
>> Although this has always been the case, it doesn't seem right to overwrite the existing access.log file if squid is updated or have I misunderstood something?
>>
>> Regards,
>>
>> Adolf.
>>
>
--
Sent from my laptop
next prev parent reply other threads:[~2024-08-13 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 15:25 Adolf Belka
2024-08-13 9:57 ` Michael Tremer
2024-08-13 11:04 ` Adolf Belka [this message]
2024-08-21 10:04 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0a558cdd-3241-4ca1-a388-2b6d0024f108@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox