Re: Squid 7.1 workers options without kernel SO_REUSEPORT param
Alex Rousskov <[email protected]> Mon, 4 Aug 2025 09:33:25 -0400
| Newsgroups | gmane.comp.web.squid.general |
|---|---|
| Message-ID | <[email protected]> |
On 2025-08-04 09:02, Clément Paulet wrote: > We use SQUID 6.3 with enable-workers option, 16 workers for our traffic. Squid has no "enable-workers" configuration option. I assume you meant the "worker-queues" option that comes with http_port and similar listening port directives. I also assume that you use "workers 16" in your squid.conf. Please correct any wrong assumptions. > How can we update to 7.1 without change our OS Kernel (based on RedHat 9) ? If your OS configuration stays the same, then, bugs notwithstanding, you should be able to upgrade Squid from v6 to v7 without adding or removing the worker-queues option. > Seems option SO_REUSEPORT mandatory since 7.x. For Squids configured with the "worker-queues" port option, SO_REUSEPORT support in OS TCP stack is mandatory since the "worker-queues" port option was added in Squid v5. For Squids configured without the "worker-queues" port option, SO_REUSEPORT support is unnecessary (and unused/ignored) in all Squids. I see no relevant changes between Squid v6 and v7. Please detail the problem you are experiencing while upgrading; it is not clear (to me) what prevents you from upgrading Squid while keeping your squid.conf the same. Thank you, Alex. _______________________________________________ squid-users mailing list [email protected] https://lists.squid-cache.org/listinfo/squid-users