At 10:24 PM -0400 6/6/01, Dan Langille wrote:
>How does htmerge dtermined whether or not a document has changed
>since the last run?
When indexing, htdig sends an If-Modified-Since header to the
server--which should only send the document if it has been modified.
Further, the date of the document is checked against that in the
database. Those that have changed are marked as such and htmerge will
go through and clear them out in favor of the new version.
>local_urls? I haven't heard of that. I'm guessing this is where htdig is
>running on the same box as the web server. If so, that applies to my
>situation. At present, I'm running via http. What should I look for in
>order to use local_urls?
See <http://www.htdig.org/attrs.html#local_urls>
>as they arrive from the mailing list. I should be able to update the index
>dynamically as well.
This is not necessarily such a great idea--you can easily get into
race-type conditions. Usually with mailing archives, I update the
archives and the index via a cron job that runs, say every hour or
so. (Making sure that the job will never run anywhere close to an
hour.)
However, it's worth noting that the new database format used in 3.2
allows much cleaner incremental indexing and with the -m flag to do a
"minimal" index of only a set of URLs, you can do essentially exactly
what you want--add a set of new URLs to the database.
--
--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
_______________________________________________
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
