7.3: Squid 6.3 with multiple workers not starting - net.unix.dgram.sendspace too low

Hi, I just upgraded to Squid 6.3 under 7.3 and noticed that it no longer starts if configured to use multiple worker processes. After some debugging I found that net.unix.dgram.sendspace with its 2k limit is the reason. Squid uses Unix sockets for IPC and sends messages larger than those 2k

7.3: Squid 6.3 with multiple workers - net.unix.dgram.sendspace too low

Hi, Today I upgraded to the brand new Squid version 6.3 from ports and noticed, that Squid no longer starts properly if configured with multiple worker processes. After some debugging the limit from net.unix.dgram.sendspace came up as cause. The 2k default is way to low. In ktrace I saw sen

Re: 7.3: Squid 6.3 with multiple workers not starting - net.unix.dgram.sendspace too low

On 19 Oct 2023 16:36, Silamael Darkomen wrote: Hi, I just upgraded to Squid 6.3 under 7.3 and noticed that it no longer starts if configured to use multiple worker processes. After some debugging I found that net.unix.dgram.sendspace with its 2k limit is the reason. Squid uses Unix sockets

Re: 7.3: Squid 6.3 with multiple workers - net.unix.dgram.sendspace too low

On 20 Oct 2023 19:33, Stuart Henderson wrote: After a few hours digging around, I eventually figured out where the relevant sockets are created and have added a patch (to 7.4-stable and -current) to bump buffers on them. Hi Stuart, Meanwhile I also did some digging and opened a bug at Squid wi