According to Malcolm Austen:
> On Tue, 6 Mar 2001, Geoff Hutchison wrote:
> + At 1:51 PM +0000 3/6/01, Malcolm Austen wrote:
> + >It's not that easy surely? The hop count is based on steps from the
> + >start_url list, not the limit_urls-to list. The hop count is also not 100%
> + >reliable at 3.1.5 (and documented as unreliable in update runs).
> + 
> + Well, it's probably pretty reliable at this point. The problem in 
> + previous versions was that in update runs, the URLs would be loaded 
> + from the database, but with no hopcount set.
...
> Certainly hopcounts are not reliable in _full_ index runs with 3.1.5 - I
> recall we (or possibly it was Gilles and I) have had some e-versation on
> the matter before and it may be about to resurface. I have just been
> adding a little extra to my report script to tabulate all the indexed
> pages by hop count (in one file per server). It is clear that 3.1.5
> doesn't always increment the hopcount for new pages. Indeed it can under
> (as yet unclear circumstances) bury quite deeply and still only have the
> hopcount set to 1. Evidence is available but I won't bore you with it
> here/now since this might be code that has changed substantially for 3.2!

Well, if you have a simple test set of data that produces this problem
in 3.1.5, then please do bore us with it.  Even though there have been
substantial changes for 3.2, much of those have been backported to 3.1.5,
so if the problem remains in 3.1.x but not in 3.2.x, I'd like to know what
the cause is, so we can address this if/when we start working on 3.1.6.

-- 
Gilles R. Detillieux              E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba  Phone:  (204)789-3766
Winnipeg, MB  R3E 3J7  (Canada)   Fax:    (204)789-3930

_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a 
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html

Reply via email to