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: [PATCH] squid: Comment out access.log in rootfile
Date: Mon, 08 Jul 2024 13:55:10 +0200	[thread overview]
Message-ID: <906254b5-7c41-442c-842b-091aadb56330@ipfire.org> (raw)
In-Reply-To: <20240708114842.4444-1-adolf.belka@ipfire.org>

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

Hi All,

Forgot to add a tag to identify that this was discovered by Peter Müller
https://lists.ipfire.org/hyperkitty/list/development(a)lists.ipfire.org/thread/QNRP6VHFPE5MSXQ45S4WLH36HRWCIYWP/

Regards,
Adolf.


On 08/07/2024 13:48, Adolf Belka wrote:
> - Everytime an update has been done on squid the access.log file has been replaced with an
>     empty file, losing whatever messages have been in the log.
> - This has been the case since squid was implemented in IPFire.
> - Update of rootfile to comment out var/log/squid/access.log
> 
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
>   config/rootfiles/common/squid | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/config/rootfiles/common/squid b/config/rootfiles/common/squid
> index 50c77a114..4f92469e3 100644
> --- a/config/rootfiles/common/squid
> +++ b/config/rootfiles/common/squid
> @@ -2345,6 +2345,6 @@ var/ipfire/updatexlrator/bin/lscache
>   var/ipfire/updatexlrator/updxlrator-lib.pl
>   var/log/cache
>   #var/log/squid
> -var/log/squid/access.log
> +#var/log/squid/access.log
>   var/log/updatexlrator
>   #var/logs

  reply	other threads:[~2024-07-08 11:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08 11:48 Adolf Belka
2024-07-08 11:55 ` Adolf Belka [this message]
2024-07-08 15:33 ` 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=906254b5-7c41-442c-842b-091aadb56330@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