From: Jim <li...@yg...> - 2004-10-23 05:34:18
|
On Thu, 21 Oct 2004, Dunson-Odusanya, Michael wrote: > [database_dir] > -rw-r--r-- 1 search 2048 Oct 20 14:18 db.accents.db > -rw-r--r-- 1 search 10362880 Oct 21 12:01 db.docdb > -rw-r--r-- 1 search 10362880 Oct 21 10:41 db.docdb.work > -rw-r--r-- 1 search 2048 Oct 21 10:41 db.docs.index > -rw-r--r-- 1 search 2048 Oct 20 14:18 db.metaphone.db > -rw-r--r-- 1 search 2048 Oct 20 14:18 db.soundex.db > -rw-r--r-- 1 search 104323392 Oct 21 12:01 db.wordlist > -rw-r--r-- 1 search 1308 Oct 21 10:41 db.wordlist.work > -rw-r--r-- 1 search 4096 Oct 21 10:41 db.words.db > > But htsearch returns "No matches found" for any search word, > this occurs both from the command line and from a web browser: In order to figure out what is going on, you probably need to take a closer look at what your rundig script is doing. Have you tried running it with two or three -v options? The sizes of some of the files listed above imply a problem with the indexing phase. In particular, it looks like your db.words.db and db.docs.index databases are empty, or nearly so. This would explain why you are not getting any hits when you test the search. Since both of these files are created by htmerge, there might be a problem there. However it also looks like your db.wordlist.work file also contains very little. Did you perhaps abort a dig while htdig was running? My suggestion would be to clear out that database directory and rerun rundig in verbose mode so that you can see what is going on. Jim |