Re: htdig - Indexing of pages

From: Date: Sat, 08 Feb 2003 12:12:07 +0000
Subject: Re: htdig - Indexing of pages
References: 1  Groups: php.mirrors 
Request: Send a blank email to php-mirrors+get-15590@lists.php.net to get a copy of this message
1. You need lots of free disk space when indexing. As I mention I had installed htdig under /usr/local/htdig where I have only 300MB free. I set up the db to /home/htdig where I have about 20GB free... It indexed everything ok but when it got to do the sorting it failed because it used temp under /usr/local/htdig. So it would be nice to mention that you need at least 3 GB free to create a working search engine (I can't really say how much space the sorting takes but I imagine it recreates the database again). Somebody might have more info on this.
Well, it would be nice to know some more precise data about needed space...
2. In my cgi-bin directory I had an old version of htsearch (compiled with different options apparently). I had to erase this file (in cgi-bin) because eventhough htphp.sh clearly states to execute $HTBINDIR/htsearch the file in cgi-bin was executed. Don't know if this was an apache issue or htdig. Somebody please test and confirm this.
Well, this is not too specific, and not confirmed, so I don't know how to write this on the site in a general way.
P.S. It would be nice to mention in mirror.php which manual languages are indexed since this should be kept by the mirror admin in HTSEARCH_EXCLUDE
The plan is to have an advanced search page soon, which interprets the HTSEARCH_EXCLUDE contents, and presents the search page according to it's contents (ie. it wont offer languages to choose from for the search which are not indexed). I don't think so that printing out HTSEARCH_EXCLUDE literally on mirror.php has any point in it for users. What do you think? Goba

« previous php.mirrors (#15590) next »