Christian Stalberg wrote:
> 
> EquivalentServer http://47.40.164.15 http://47.154.144.5
> EquivalentServer http://47.154.144.46 http://47.154.144.117
> EquivalentServer http://47.155.65.163 http://47.2.9.89
> EquivalentServer http://47.192.1.8 http://47.73.7.31
> EquivalentServer http://47.80.11.234 http://47.173.32.36
> EquivalentServer http://47.154.145.79
> #(default nothing)  This allows you to deal with
> #servers that use respond to multiple DNS names.  Each line should have
> #a list of all the method/names that should be considered equivalent.
> #If you have multiple directives, each one defines its own set of equivalent
> #servers.

My guess is that you are confused on how EquivalentServer works (this is
based on the last EquivalentServer, since that directive with a single
server does nothing).

EquivalentServer A B C
tells the spider to treat servers A, B and C as single logical server.

EquivalentServer A B
EquivalentServer C D
tells the server to treat A and B as one logical server and C and D as
another logical server.  Note that there is no relation between logical
server A-B and logical server C-D.

Also, EquivalentServers are not transitive.  Just because servers A and
B are equivalent and servers a and c are equivalent, does not make
servers B and C equivalent.

Consider the configuration:

EquivalentServer A B
EquivalentServer A C

If your spider starts on server A, it will also spider both servers B
and C.  But if your spider starts at B it will spider A but not C.

Does this help?

moo
----------------------------------------------------------------------
          Ron Klatchko - Manager, Advanced Technology Group           
           UCSF Library and Center for Knowledge Management           
                           ron@ckm.ucsf.edu