Another question from me regarding peers:
I would like to configure squid like this:
When everything is ok:
for 1 top level domain go direct.
for everything else go through peer.
When direct connection dies it should:
for everything go through peer.
I tried configuring 3 squid's, one going only through parent,
one going only through peer and third connecting to these two.
Config of 'third' was:
cache_peer w3cache-dir.com sibling 3131 3131 allow-miss weight=3
cache_peer w3cache-w3c.com parent 3133 3133 allow-miss default weight=1
neighbor_type_domain w3cache-w3c.com sibling .pl
neighbor_type_domain w3cache-dir.com parent .pl
never_direct allow all
This is last config, there were many attempts :)
Most close to ideal was configuring both as parents, and one (direct) more weighted and
'never_direct allow all' setting.
But still there were quieries to w3cache-w3c. Can I configure it better? (all
queries should go to w3cache-dir when it's working (w3cache-w3c is much slower for
this top level domain))
-- Daniel Fenert --==> daniel@fenert.net <==-- ==-P o w e r e d--b y--S l a c k w a r e-=-ICQ #37739641-== When things go well, expect something to explode, erode, collapse or just disappear. =======- http://daniel.fenert.net/ -=======< +48604628083 >Received on Thu May 29 2003 - 05:09:25 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:17:06 MST