According to Geoff Hutchison:
> On Thu, 22 Apr 1999, denis filipetti wrote:
> 
> >     I just tried 3.1.2 and got the following output. Running htdig from b4 a
> > second later worked like a champ. THis output is with this verbosity arg:
> > -vvvvvvvvvvvvvvvvv. Any ideas ?
> 
> I don't know what I'm supposed to see as the problem... For one, it seems
> like you haven't set some of the config attributes, like maintainer: and
> user_agent:
> 
> > Read 7358 from document
> > Read a total of 7358 bytes
> >  retrieved but not changed
> > pick: <insert node name here>, # servers = 1
> 
> This is actually an improvement in 3.1.0 and later. If you have a URL in
> the database already and it *hasn't* changed, it doesn't bother re-parsing
> it. So it grabbed the file mentioned, saw it already had it in the db with
> the same date and knew it was done.
> 
> Why do repeat work?
> 
> If you're telling me that it *has* changed, then there's another problem.

I didn't see any Last-Modified headers in the output Denis sent.  If the
server isn't sending any, that can be a problem.  If reconfiguring or
replacing the server isn't an option, then you may need to set the
modification_time_is_now attribute to true, but then update digs will
always re-dig everything, if I'm not mistaken.

In any case, I think the database format has changed between 3.1.0b4 and
3.1.2, so you should rebuild from scratch after upgrading.

-- 
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
------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.

Reply via email to