On 12/04/2017 12:04 PM, carlos wrote:
> Like i have worker > 1 its an SMP setup , correct?
Correct. "worker > 1" is sufficient (but not necessary) to enable SMP.
> Probably i should be missing the -n
The -n command line option is essentially required to run multiple SMP
instances using the same Squid binary. -n can also make it easier for
multiple SMP instances to share the same squid.conf, but that
simplification is a side effect.
> that config is the config file of the
> first instance, the other instance is more or less the same, but:
> pid_filename (/var/run/squid.pid vs /var/run/squid81.pid)
> http_port (80 vs 81)
> visible_hostname (squid_80_${process_number} vs squid_81_${process_number})
> access_log (/var/log/squid-80/access80_${process_number} vs
> /var/log/squid-81/access81_${process_number} )
> cache_log (/var/log/squid-80/cachelog80_${process_number} vs
> /var/log/squid-81/cachelog81_${process_number})
FYI: You may be able to use the same squid.conf for both instances if
you use something like "-n 80" and "-n 81" to start your two Squid
instances and replace 80 and 81 in squid.conf with ${service_name} as
Amos suggested. Again, that unification is sometimes nice to have, but
-n is actually needed for other reasons -- it affects various SMP paths
that cannot be configured via squid.conf.
> In RHEL i start squid with systemctl start squid.service and systemctl
> start squid81.service.
> This is multi-instance, correct?
Correct.
> i think i followed https://wiki.squid-cache.org/MultipleInstances.
The SMP section in that document needs adjustment: It currently focuses
on what -n means. It should focus on specifying that -n is *required*
for running multi-instance SMP Squids using the same binary (and
referring elsewhere for -n documentation).
> Can you confirm that in squid config is OK?
It may be OK, but you need -n to make it work.
HTH,
Alex.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
