Hello,
are used.
I have a similar configuration: two SMP squids running on the same OEL host.
They were built with different configurations: with different installation path prefixes and different names of binary files: squid and squid.user and they listen to different ports.
They are launched from two different services: squid.service and squid.user.service with the service Type=forking:
ExecStart=/usr/sbin/squid -sYCExecStart=/sbin/squid.user -f /etc/squid.user/squid.conf
I have not experienced any troubles with this configuration yet.
> Please be aware that "squid -n ..." is a REQUIREMENT for running
multiple Squid instances on the same machine regardless of what featuresare used.
Could you please tell me if I should use the -n option in the ExecStart strings?
The arguments of the options should be the service names?
ExecStart=/usr/sbin/squid -sYC -n squid.serviceExecStart=/sbin/squid.user -f /etc/squid.user/squid.conf -n squid.user.service
Kind regards,
Ankor.
чт, 6 мар. 2025 г. в 04:07, Amos Jeffries <squid3@xxxxxxxxxxxxx>:
On 6/03/25 13:16, Lubos Uhliarik wrote:
>
> In the end, we discovered that a customer was running two Squid
> instances on the same
> machine—one SMP instance with 16 workers and one single-process
...
>
> The fix is simple—just specify a service name using the -n Squid
> parameter for
> one of the Squid instances.
>
Please be aware that "squid -n ..." is a REQUIREMENT for running
multiple Squid instances on the same machine regardless of what features
are used.
There are a very large number of possible error signs that may (or not)
be visible if it is omitted.
Cheers
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.squid-cache.org/listinfo/squid-users
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx https://lists.squid-cache.org/listinfo/squid-users
