Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Harrell, Roger <rjharrel@be...> - 2004-02-19 17:37:46
I got HtDig installed on a Red Hat 9 box using the Red Hat Binaries. Kicking
off the default rundig (with pointer changes for directories, and a slightly
modified htdig.conf file) it appears to do the dig properly, then it starts
WordKey::Compare: key length for a or b < info.num_length
several hundred times and ends with:
WordDB: /var/www/htdig/db/db.words.db: page 0: reference count overflow
The rundig is somewhat different than the rundig on the version I have
running on another machine so I'm not sure what is occurring here. There is
a call to htpurge instead of htmerge. What is htpurge?
According to Harrell, Roger:
> I got HtDig installed on a Red Hat 9 box using the Red Hat Binaries. Kicking
> off the default rundig (with pointer changes for directories, and a slightly
> modified htdig.conf file) it appears to do the dig properly, then it starts
> WordKey::Compare: key length for a or b < info.num_length
> several hundred times and ends with:
> WordDB: /var/www/htdig/db/db.words.db: page 0: reference count overflow
Red Hat 9 installs the 20021103 snapshot of the 3.2.0b4 development code,
which is a year older and a bit more buggy than the current 3.2.0b5 release.
If you want a 3.2 beta release, for the new features it provides, you should
upgrade to the latest one. I don't know if it's available as a rh9 RPM,
but you could try backporting the Fedora Core development source RPM for it.
If you don't need 3.2, you can use the htdig316*-3.1.6-1.rh9.i386.rpm
packages from http://www.htdig.org/files/binaries/ . If you use these,
I should point out that when you install the htdig316 RPM packages,
you should first remove the htdig and htdig-web packages (with rpm -e)
that were installed from the Red Hat distribution, as the two packages
will clash with each other if you try to have both on at the same time.
(I used a different package name so that up2date wouldn't keep trying to
get you to "upgrade" from 3.1.6 to Red Hat's cruddy 3.2.0 beta snapshot
> The rundig is somewhat different than the rundig on the version I have
> running on another machine so I'm not sure what is occurring here. There is
> a call to htpurge instead of htmerge. What is htpurge?
That other machine is likely running one of the 3.1.x releases, hopefully
3.1.6. This is the latest "stable" release, although the 3.2.0b5 code
is getting close to being ready for a stable release. The two lines are
quite different, though, in how their DBs are structured. 3.1.x uses
htmerge after htdig, to merge wordlist entries together, and build a
db.words.db file from the merged wordlist, as well as purging records for
URLs that htdig couldn't index for whatever reason. In 3.2, htdig manages
db.words.db directly, so all that's needed after htdig finishes is to
purge out the stale entries, which is what the new htpurge utility does.
htmerge is now just used for merging together two separate databases,
with the "-m" option, which was a secondary function of htmerge in 3.1.x.
Hope this clears some of the confusion.
Gilles R. Detillieux E-mail: <grdetil@...>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/
Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada)