public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 186 overwrites latest Squid access.log file
Date: Mon, 17 Jun 2024 10:29:10 +0200	[thread overview]
Message-ID: <72edb8c4-822a-477c-a865-7a436a29b516@ipfire.org> (raw)
In-Reply-To: <f5d99108-9b92-4df1-9d08-4a20b5beb820@ipfire.org>

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

Hi Peter & all,

On 16/06/2024 16:08, Peter Müller wrote:
> Hello *,
>
> while installing stable Core Update 186, I noticed that it ships
> /var/log/squid/access.log, which will effectively overwrite the latest
> Squid access log file with an empty file.
This has been done for a long time. I got back to Core Update 100 and it 
was being done then already. It may have been done since squid was 
started in IPFire.
> This is not something we want to do, but I defer to your judgement
> whether or not this warrants a rebuild of stable Core Update 186. :-)
If it is something that should not be done, and from the description I 
would agree with that, then it should be changed but I think it can wait 
for Core Update 187 as we have been living with it for at least 8 years 
already.

Just went back to the earliest Core Update in the git repo, which is 
Core Update 30, and that also ships the access.log file so effectively 
it has been done for ever.

Regards,
Adolf.
> Thanks, and best regards,
> Peter Müller

-- 
Sent from my laptop


      reply	other threads:[~2024-06-17  8:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16 14:08 Peter Müller
2024-06-17  8:29 ` Adolf Belka [this message]

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=72edb8c4-822a-477c-a865-7a436a29b516@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