According to Aviram Carmi: > At 5:38 AM -0600 on 10/17/02 Jim Cole wrote: > > Aviram Carmi's bits of Tue, 15 Oct 2002 translated to: > >>I am new to HtDig. HtDig was installed with Red Hat 7.3 and seems to > >>execute just fine. > >> > >>I just created a new config file and I am currently testing it. > >> > >>the search form is at http://www.knx1070.com/search.html > >> > >>the config file is at http://www.knx1070.com/htdigknx.config.txt > >> > >>I have several problems with finding the "appropriate" pages. > >> > >>For example, searching for "drama hour" does not bring up the > >>"drama.html" page, even though the phrase "knx drama hour" is all > >>over the page (title/H1/alt/keywords/description/links to the page > >>from other pages) > > > > I am not familiar with how Red Hat sets things up, but something > > seems to be wrong with your current setup. The result page doesn't > > include either the header or footer. If the footer was present, you > > would most likely have links to additional result pages that would > > include the page you are looking for. Try doing a search on the > > ht://Dig site and notice the information/search boxes at the top of > > the page and the result page links at the bottom. There are the > > header and footer sections that I am referring to. > > > > Did you at some point try to customize your result templates? > > no, I only created a copy of the default config file, and edited it > to change the start URL, added more weight to the title and headers > (trying to force the drama hour to show up, since it is the only one > that has "drama hour" in the <title> and <h1> > > I did not touch the rest of the config file.
OK, but what about the template files? Did you change them or move them around? > >>similarly, searching for "zabba" brings up pages with WSB, Sub, > >>seebee, sabe, before bringing up the page with "zabba"...??? > > > > I would work on fixing the header/footer issue first. A default > > header will give you additional information about what terms are > > actually being searched on. That might provide a clue as to the > > other problems you are encountering. It might be that htdig is > > not even using the config file that you customized. Are you > > passing the name of your custom config file to rundig (or htdig) > > using the -c options? > > I created a clone of rundig, and customized it to use the appropriate > directory /var/lib/htdig/knx so that I will not have conflicting db > files. (I guess this can be done via a config parameter) and maybe it > is not finding its templates because I changed the directory... I'll > look into it. thanks. > > I run it using 'rundigknx -v -c /etc/htdigknx.conf' If you moved the database directory around in your copy of the rundig script, then you need to make the corresponding change to database_dir. See http://www.htdig.org/FAQ.html#q4.4 and http://www.htdig.org/rundig.html (section on Customization). ... and in the next message ... > At 11:50 AM -0500 10/17/02, Gilles Detillieux wrote: > > According to Jim Cole: > >> Aviram Carmi's bits of Tue, 15 Oct 2002 translated to: > > > > This behaviour doesn't jive with the config file you posted a day or two > > ago. > > I know, that is why I am lost, it does not seem to use the right > config parameters. > > Initially I did have soundex/metaphone/spelling enabled, but after > failing my test, I deleted all databases, modified the config file, > and rundig (actually rundigknx, which is a clone of rundig) again. I > think that I renamed /etc/htdig.conf to htdig.conf.ORIG, to make sure > it is not found. I'll review what I am doing and report back, Red Hat's RPMs define CONFIG_DIR as /etc, so that's were all config files should be if they're to be accessed by htsearch. When you set the "config" input parameter to "something", htsearch will use /etc/something.conf as the config file. So, I see that the value of config that you're using in your search form is "htdigknx", so what is the value of search_algorithm in /etc/htdigknx.conf? It can't be the same file as http://www.knx1070.com/htdigknx.config.txt. Also, I noticed just now that in http://www.knx1070.com/htdigknx.config.txt, the lines aren't properly terminated. They end with only CR, not LF or CR/LF. On Unix/Linux, you need LF line terminators, and ht://Dig is no exception. So, if that is your config file, htsearch won't read anything from it. Which makes me wonder where htsearch is seeing the search_algorithm setting that enables soundex or other fuzzy matches. -- 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: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm _______________________________________________ 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
