On 07.10.11 20:30, Momen, Mazdak wrote:
>How can I create a squid cluster that would ideally share log files
> and replicate config changes to each other? We have a load balancer
> that can handle sending requests to one or the other server but I
> would prefer to not have to have someone log into each squid server
> to change the ACL, is there a better way to handle this?
We manage a small squid server farm.
We have defined hostnames like "proxy", "proxy-sibling1" etc to
/etc/hosts on all machines with proper IP's and use there in squid
config file for directives like http_port, tcp_outgoing_address, cache_peer
and udp_incoming_address.
Now we have nearly unique config file - the only directive that differs
is unique_name. Even this mmight change, when squid stops deriving
unique_name from visible_name, see:
http://bugs.squid-cache.org/show_bug.cgi?id=2654
When we change acl's, we distribute new config file (maintained in svn)
to all servers and issue reload.
We do not share caches not logfiles - that would take some work to
maintain.
-- Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Eagles may soar, but weasels don't get sucked into jet engines.Received on Thu Oct 20 2011 - 08:16:18 MDT
This archive was generated by hypermail 2.2.0 : Thu Oct 20 2011 - 12:00:03 MDT