From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] squid: Update to 5.2
Date: Sat, 09 Oct 2021 15:00:57 +0200 [thread overview]
Message-ID: <d51478cf-90da-fc1b-5daa-d01d0e91f1e9@ipfire.org> (raw)
In-Reply-To: <98C14971-3FDC-4106-909C-14672C77153C@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2115 bytes --]
Hi,
On 09.10.2021 14:47, Michael Tremer wrote:
> Hello,
>
> I would say that 16k should be fine. 32k would be even better.
>
> It probably only becomes a problem on a very busy proxy with a lot of open (but idle) connections.
This leaves me in the state "Remove or not?" ;-)
My two cents: Let the user decide and leave this setting as it is...
Opinions?
Matthias
> -Michael
>
>> On 9 Oct 2021, at 13:46, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>
>> Hi,
>>
>> On 09.10.2021 14:06, Michael Tremer wrote:
>>> Hey,
>>>
>>> Are we ready to got to squid 5, yet?
>>
>> Up and running here, but...
>>
>>> I thought there were some remaining changes required in the CGI file?
>>
>> ...the question is whether we adopt the new maximum of 32k
>> filedescriptors as a fixed setting and remove the corresponding
>> adjustment field or leave the user the possibility to influence these
>> settings via GUI.
>>
>> I'm testing here with '16384' and didn't see any problem with that. If
>> it is desired I can of course remove the setting, I just didn't see the
>> need so far.
>>
>>> -Michael
>>>
>>>> On 8 Oct 2021, at 18:19, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>>
>>>> For details see:
>>>> http://www.squid-cache.org/Versions/v5/changesets/
>>>>
>>>> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
>>>> ---
>>>> lfs/squid | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/lfs/squid b/lfs/squid
>>>> index c56dca7de..5e9648aba 100644
>>>> --- a/lfs/squid
>>>> +++ b/lfs/squid
>>>> @@ -24,7 +24,7 @@
>>>>
>>>> include Config
>>>>
>>>> -VER = 5.1
>>>> +VER = 5.2
>>>>
>>>> THISAPP = squid-$(VER)
>>>> DL_FILE = $(THISAPP).tar.xz
>>>> @@ -46,7 +46,7 @@ objects = $(DL_FILE)
>>>>
>>>> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>>>
>>>> -$(DL_FILE)_MD5 = 17be9709b54fe0146452113404be7b54
>>>> +$(DL_FILE)_MD5 = 102984f3ea382a1fa5bd917c2ee155ec
>>>>
>>>> install : $(TARGET)
>>>>
>>>> --
>>>> 2.18.0
>>>>
>>>
>>
>
next prev parent reply other threads:[~2021-10-09 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 17:19 Matthias Fischer
2021-10-09 10:57 ` Adolf Belka
2021-10-09 12:06 ` Michael Tremer
2021-10-09 12:46 ` Matthias Fischer
2021-10-09 12:47 ` Michael Tremer
2021-10-09 13:00 ` Matthias Fischer [this message]
2021-10-14 19:24 ` 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=d51478cf-90da-fc1b-5daa-d01d0e91f1e9@ipfire.org \
--to=matthias.fischer@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