From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Core Update 186 overwrites latest Squid access.log file
Date: Sun, 16 Jun 2024 14:08:00 +0000 [thread overview]
Message-ID: <f5d99108-9b92-4df1-9d08-4a20b5beb820@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
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 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. :-)
Thanks, and best regards,
Peter Müller
next reply other threads:[~2024-06-16 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 14:08 Peter Müller [this message]
2024-06-17 8:29 ` Adolf Belka
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=f5d99108-9b92-4df1-9d08-4a20b5beb820@ipfire.org \
--to=peter.mueller@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