This weekend I converted from Squid 2.5STABLE14 to 2.6STABLE5-20061114. I have four proxy servers, each of which use a virus scanner as a parent cache. The virus scanner runs on the same machine as the squid process. Here's what my cache_peer lines looked like under 2.5: cache_peer 127.0.0.1 parent 8080 7 no-query no-digest default cache_peer proxy02 parent 8080 7 no-query no-digest round-robin cache_peer proxy03 parent 8080 7 no-query no-digest round-robin cache_peer proxy04 parent 8080 7 no-query no-digest round-robin cache_peer proxy02 sibling 80 3130 proxy-only cache_peer proxy03 sibling 80 3130 proxy-only cache_peer proxy04 sibling 80 3130 proxy-only This configuration let my squid process use the virus scanner on the same machine as a parent, but if the virus scanner stopped working for whatever reason, squid would use the virus scanner on one of the other three proxy servers. Squid also used the squid process on the other three machines as siblings, sharing their cache. When I converted to 2.6STABLE5-20061114, this configuration was no longer accepted. Squid core dumped, and complained about cache peer 'proxy02' being used twice. Is this a bug or a feature? While I have 'proxy02' defined twice, it's on different port numbers. How do I get the equivalent function out of 2.6? Here's what I'm using now: cache_peer 127.0.0.1 parent 8080 7 no-query no-digest default cache_peer proxy02 sibling 80 3130 proxy-only allow-miss cache_peer proxy03 sibling 80 3130 proxy-only allow-miss cache_peer proxy04 sibling 80 3130 proxy-only allow-miss This seems to work, but I may be getting some forwarding loops. Mike Mitchell SAS Institute Inc. Mike.Mitchell@xxxxxxx (919) 531-6793
