I used the /usr/local/bin/rundig file which seems to have worked. However, I did not pipe the output to a file : (
-rw-r--r-- 1 root wheel 1.6G Dec 23 20:39 db.docdb -rw-r--r-- 1 root wheel 2.0k Dec 23 18:55 db.docs.index -rw-r--r-- 1 root wheel 163M Dec 23 18:55 db.wordlist -rw-r--r-- 1 root wheel 105M Dec 23 18:55 db.words.db
The file stats look a bit suspicious. It might be that some phase of the indexing run simply failed and left you with a corrupt set of databases. Or perhaps you just have things configured in a manner very different from what I am used to.
The htsearch in cgi-bin loads up fine but I cannot find any words at all
whatsoever, no matter what I search for.
I have now increased the size of the following defaults, but not yet re-run the rundig script because I know it is going to take days....
#max_head_length: 10000 max_head_length: 100000
#max_doc_size: 200000 max_doc_size: 2000000
The max_head_length attribute doesn't affect the terms indexed; it only affects how much text is saved for excerpts. The max_doc_size attribute has the potential to affect the terms indexed, but not in a manner that would easily explain the fact that you can't find any terms. A possible exception might be document types that require preprocessing (e.g. PDFs), however if that were the case, I don't think you would be seeing a 1.6 GB database file.
The problem is that is going to take days to run and might not help.
If you have to take another run at it, you might want to start with a smaller dig in order to verify at least basic functionality.
So, my question is "WTF is in that 1.6 gig database and how do I know in
advance what the current problem is so that I can fix it?"
You might want to try playing with htdump (http://www.htdig.org/htdump.html) in order to determine what is in the database. As for the problem, you might want to start be ensuring that you have plenty of free disk space, both on the partition containing your databases and the partition used for sorting. I believe in most cases the default for the latter is the partition on which /tmp resides.
Jim
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ ht://Dig general mailing list: <[EMAIL PROTECTED]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
