According to Sunny Fortune: > > As it turns out, the first htmerge pass, after > > htdig, is needed on each > > database before you run htmerge -m. The code that > > handles the merging > > of two databases expects that the wordlist has > > already been purged of > > control records that htdig uses to tell htmerge > > about documents to update > > or delete. > > What does "already been purged of control records" > mean?
Essentially it means you've already run htmerge after htdig. htdig puts not only words in db.wordlist, but also some control records which tell htmerge to clear out certain records from the database. htmerge only expects and understands these records when run without the -m option. If you run htmerge -m and the wordlist for the database you're merging has some of these control records, their DocIDs don't get adjusted so htmerge ends up clearing out the wrong records from the database. > I am presently running digs on each of my site and > then finally performing a merge to one of the sites. > Example, > htdig -c site1.conf > htdig -c site2.conf > htdig -c site3.conf > > htmerge -c site1.conf > htmerge -c site1.conf -m site2.conf > htmerge -c site1.conf -m site3.conf > > So the search is performed on the merged database at > site1. > > Isn't this also a correct method? No. You must also run "htmerge -c site2.conf" and "htmerge -c site3.conf" before merging sites 2 and 3 into 1. Otherwise, you run the risk of losing some site1 records, possibly some valid site2 records, and maybe even some valid site3 records as well. -- 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 _______________________________________________ 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
