At 9:45 AM -0500 4/10/01, Russell Turpin wrote:
>(a) How much administration does htdig typically require, after
>intitial setup and testing?
Little, if any.
>(b) What about its databases? Do they ever become corrupt, for
>example, when the server crashes during a merge? Do they ever
Crashing during a merge would be a bad thing. Yes, there does seem to
be periodic bit-rot seen by some users. It has been hard for us to
track down any root causes for this. Any help is of course greatly
appreciated.
>need rebuilding from scratch? What administration tools are there
>to examine, validate, and repair these databases? (I don't see
>any documented on the website, which is either a good sign or a
In most cases, it's ideal to work on alternate copies of the
databases--if something goes wrong during merge, usually the sizes of
the databases would be drastically different. As far as "repair,"
this would require some sort of checksum or error-correcting code in
the databases. While this is a good idea, it is not, at present,
provided.
>(c) Obviously, htdig gets embedded in web applications. But has
>anyone ever used it in a turnkey application delivered to
>customers who are not savvy in administering websites?
I believe there have been certain applications in this area.
>(d) What configuration and use practices are recommended and
>or cautioned against, for this kind of purpose?
Work using the -a flag and consider the state of the databases.
Rebuild from scratch periodically to be on the safe side. (If you use
the -a flag, ala my rundig.sh script rebuilding from scratch will
occur if no .work files exist.)
--
--
-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
