From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Are you by any chance working on Squid 5.4? :-)
Date: Thu, 10 Feb 2022 17:25:22 +0000
Message-ID: <62391045-3581-cb71-e9c2-26c05728b3dc@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1068211954346173962=="
List-Id: <development.lists.ipfire.org>

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

Hello Matthias,
hello *,

by coincidence, I just stumbled across a Squid 5.4 source tarball on source.i=
pfire.org:

> pmueller(a)people01:~$ ls -lah /pub/sources/source-2.x/squid-5.*
> -rw-r--r-- 1 mfischer people 2.5M Aug  2  2021 /pub/sources/source-2.x/squi=
d-5.1.tar.xz
> -rw-r--r-- 1 mlorenz  people 2.5M Oct  6 07:44 /pub/sources/source-2.x/squi=
d-5.2.tar.xz
> -rw-r--r-- 1 mfischer people 2.5M Dec  7 18:42 /pub/sources/source-2.x/squi=
d-5.3.tar.xz
> -rw-r--r-- 1 mfischer people 2.5M Feb  7 17:10 /pub/sources/source-2.x/squi=
d-5.4.tar.xz

I therefore presume you are working on this one. :-)

While Squid 5.2, as it is now present in the upcoming Core Update 164, works =
fine, I
observed at least one memory leak in it that eventually caused swapping on a =
productive
infrastructure (under high load). Squid 5.4 should have that fixed.

Because of this, I'd like to have Squid 5.4 in Core Update 164, so our users =
won't have
to suffer from this bug. It is good to see you are taking care of it. Please =
do not feel
pressured in any way, I just thought I mention this to you. :-)

Thanks in advance for your efforts, and best regards,
Peter M=C3=BCller

--===============1068211954346173962==--