> database but used the one created in the first run) the program > appeared to function correctly. A subsequent cron run produced the > errors above.
This has been reported a number of times, but it's rather hard to track down the exact problem. It seems to be an intermittent problem for some users of ht://Dig 3.2.0 betas, but a reindex always seems to fix it. > So any help to a "quick" solution would be greatly appreciated. Are you sure they really need to be using a beta of 3.2? A "quick" fix may be to use 3.1.6, the version recommended for production use. <http://www.htdig.org/RELEASE.html> -- -Geoff Hutchison Williams Students Online http://wso.williams.edu/ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf _______________________________________________ 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
