On 25/10/11 02:39, jiluspo wrote:
Remedy I have is making name in host file. Is there any other squid configurations that I might need?
Some more description of your particular problem so we can answer would be good. Proxies peering with hosts/DNS entries to connect them describes the Internet.
I assume you mean 2 Squid instances running on the same machine. Linked as siblings to share objects. Correct?
In which case, hosts file is irrelevant. cache_peer for squid-A only needs to point at squid-B. And squid-B config file cache_peer entry points at squid-A.
Squid version matters, squid-3.1 and older require different listening ports. So the cache_peer point at the IP (usually localhost, but not required) and unique http_port value of the other sibling.
squid-3.2 has a very different multi-instances setup.
-----Original Message----- From: jiluspo How to make them sibling to each other. Does it needs name tagging or soft of? It says cache_peer 127.0.0.1 used more than once or some kind of(I forgot, currently just use 2 instances).
"It" being what? Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.16 Beta testers wanted for 3.2.0.13
