On 2025-03-06 08:59, Amos Jeffries wrote:
On 6/03/25 19:17, Andrey K wrote:
Hello,
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 -sYC
ExecStart=/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 features
are 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.service
ExecStart=/sbin/squid.user -f /etc/squid.user/squid.conf -n
squid.user.service
Yes you should. The different ./configure options has helped you avoid
major issues, but some may still appear.
I agree. Moreover, I do not understand how your two SMP Squids could
work correctly without distinct service names because (on OEL) I would
expect them to share the same shared memory segments (which they must
not do to remain distinct instances).
What is your Squid version? Can you tell how your Squids name their
shared memory segment "files"? For example, on some Linux OSes, those
segments could be in /var/run/shm/ with names like
squid-tr_map_anchors.shm and squid-tr_spaces.shm.
Thank you,
Alex.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.squid-cache.org/listinfo/squid-users
