According to Ted Stresen-Reuter: > Umm... I'm just using the rundig.sh script that came with the 3.1.6 > distribution (or that I downloaded from htdig.org). > > The line for running htfuzzy is commented out. Should it be enabled? I > didn't realize I was using any soundex or synonym search methods... I'll > have to check my config file...
The commented out call to htfuzzy in contrib/examples/rundig.sh is for rebuilding the soundex database, which must be done every time you reindex, but only if you're actually using soundex in your setting of search_algorithm. (Same goes for metaphone and accents.) However, the endings and synonyms databases only need to be built once, when ht://Dig is first installed, unless you update their respective dictionary files in which case you should rebuild. So, rundig.sh doesn't rebuild these, as rundig.sh is designed for update digs. The assumption is that you'll run the standard rundig script, installed in your BIN_DIR along with htdig et al., at least once before running the update script. The htdig.conf file that's installed by default includes both endings and synonyms in its search_algorithm setting, so you need to build these DBs. ... and later... > Acutally, it might be helpful if I sent the complete error... > > [Sun Nov 17 04:02:05 2002] [notice] Apache/1.3.23 (Unix) (Red- > Hat/Linux) mod_ssl/2.8.7 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.3.0-dev > mod_perl/1.26 configured -- resuming normal operations > [Sun Nov 17 04:02:05 2002] [notice] suEXEC mechanism enabled (wrapper: > /usr/sbin/suexec) > [Sun Nov 17 04:02:05 2002] [notice] Accept mutex: sysvsem (Default: > sysvsem) > DB2 problem...: /var/htdig/common/synonyms.db: No such file or directory > DB2 problem...: /var/htdig/common/word2root.db: No such file or directory > DB2 problem...: /var/htdig/common/synonyms.db: No such file or directory > DB2 problem...: /var/htdig/common/word2root.db: No such file or directory > [... for about 200 lines ...] > > Note that although rundig.sh runs every night, there is only one entry > like this in error_log and it is from a couple of days ago... rundig.sh won't be making any entries in your web server's error_log file unless you're running it from the web server (rather than a cron job or the command line). Those error messages above are generated whenever htsearch is run from your web server, because htsearch can't find the databases it needs for the selected search_algorithm settings. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ 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
