public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <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	[thread overview]
Message-ID: <62391045-3581-cb71-e9c2-26c05728b3dc@ipfire.org> (raw)

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

Hello Matthias,
hello *,

by coincidence, I just stumbled across a Squid 5.4 source tarball on source.ipfire.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/squid-5.1.tar.xz
> -rw-r--r-- 1 mlorenz  people 2.5M Oct  6 07:44 /pub/sources/source-2.x/squid-5.2.tar.xz
> -rw-r--r-- 1 mfischer people 2.5M Dec  7 18:42 /pub/sources/source-2.x/squid-5.3.tar.xz
> -rw-r--r-- 1 mfischer people 2.5M Feb  7 17:10 /pub/sources/source-2.x/squid-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üller

             reply	other threads:[~2022-02-10 17:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 17:25 Peter Müller [this message]
2022-02-10 18:00 ` Matthias Fischer
2022-02-11  8:39 ` Matthias Fischer

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=62391045-3581-cb71-e9c2-26c05728b3dc@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