From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: squid 5.1 gone stable Date: Wed, 18 Aug 2021 18:42:02 +0200 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5554205177953476840==" List-Id: --===============5554205177953476840== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 sam= e. >=20 > This is to protect the system from going crazy by having too many open file= s (because I think the file descriptor table used to be of a static size in o= lder versions of the kernel). >=20 >>> I suppose this is enough and I can live with 32k. We should remove the fi= eld from the UI then. >> Me too, but are 4096 enough? > No. I don=E2=80=99t know why the squid team isn=E2=80=99t handling this bet= ter. We are hitting this problem every time we update to a new version. >=20 > I suppose this is fine for testing. >=20 > You can try adding =E2=80=9Culimit -n 32768=E2=80=9D to the squid init scri= pt 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" ... For my 'cache_peer' problem I opened a bug report (https://bugs.squid-cache.org/show_bug.cgi?id=3D5147). Work in progress. Best, Matthias --===============5554205177953476840==--