Something seems wrong with the MaxHops. I am indexing the site
http://www.washtimes.com/
with MaxHops=2. This is done in order to have only recent articles in the
index, because
document dates send by an HTTP server and recorded by ASPSeek are useless.

Lets take an article
http://www.washtimes.com/entertainment/20020612-26696185.htm. This
article is reachable in 2 hops from the front page (via "Entertainment") and
so should've been
indexed, at least with "index -o" option. However, the page is not there.
When I set
MaxHops=1, 96 pages are indexed, not only the front page as might be
expected if we
count levels, instead of hops.

Am I counting hops wrong? Or there is some quirk known to the insiders?
Inquiring minds
want to know.

        Gregory Kozlovsky

Project Manager for Information Systems                 Tel: +41 (0)1 632 63
70
International Relations and Security Network (ISN)      Fax: +41 (0)1 632 14
13
Center for Security Studies and Conflict Research       Email:
[EMAIL PROTECTED]
Swiss Federal Institute of Technology (ETH)             http://www.isn.ch
Leonhardshalde 21, ETH-Zentrum / LEH
CH-8092 Z�rich, Switzerland


Reply via email to