Hello,
On 18 Aug 2021, at 17:42, Matthias Fischer matthias.fischer@ipfire.org wrote:
Hi,
On 16.08.2021 11:40, Michael Tremer wrote: ...
What makes me wonder: during build, 'squid' says it can open '32768', during start its '4096'. If someone knows why, please enlighten me... ;-)
4096 is the default maximum number of files any process can open at the same.
This is to protect the system from going crazy by having too many open files (because I think the file descriptor table used to be of a static size in older versions of the kernel).
I suppose this is enough and I can live with 32k. We should remove the field from the UI then.
Me too, but are 4096 enough?
No. I don’t know why the squid team isn’t handling this better. We are hitting this problem every time we update to a new version.
I suppose this is fine for testing.
You can try adding “ulimit -n 32768” to the squid init script and then it should be able to open up to 32k files.
...
Thanks for the clarification - I tested this with 'squid 5.1'. It seems to work:
... case "1$" in start) ulimit -n 32768 getpids "squid" ...
What is “getpids” good for?
Adding the ulimit call to the initscript and removing the configuration option from the CGI script is fine with me.
For my 'cache_peer' problem I opened a bug report (https://bugs.squid-cache.org/show_bug.cgi?id=5147). Work in progress.
I didn’t get it, but I am sure you know what you are doing :)
It is good to work together with upstream.
-Michael
Best, Matthias