Hi - For a basic index, there isn't much involved in modifying your config file. Just open htdig.conf with your favorite editor and look for an attribute named 'start_url'. Change the value of that attribute to the starting URL for your dig (e.g. http://www.yoursite.com/). Then execute rundig with verbose output (e.g. rundig -vvv). If you continue to have problems, carefully read the verbose output; most likely it will point you in the direction of the problem.
Jim perl is's bits of Tue, 9 Jul 2002 translated to: >Thanks for your mail. > >The problem I have is that I don't know how to change >the htdig.conf file. So the index db.wordlist never >be created. > >Would you please provide me an example on how to >change the htdig.conf and the htdig could find pages >and index them if you have time? > >Thanks again for your help. > >Ping >7/9/02 > >--- Jim Cole <[EMAIL PROTECTED]> wrote: >> perl is's bits of Mon, 8 Jul 2002 translated to: >> >> ... >> >/www/htdig/bin/rundig, now I received the following >> >error message: >> > >> >htmerge: Unable to open word list file >> >'/www/htdig/db/db.wordlist'. >> >Did you index anything? >> >Check your config file and try running htdig again. >> > >> >Here are the question: how to do the index? >> >> The rundig script will handle the indexing. The >> error message >> implies that htdig was unable to retrieve any >> documents. Try >> executing rundig with -vvv so that you can get a >> better idea >> of what htdig it is trying to do and where it is >> failing. >> >> Jim >> > > >__________________________________________________ >Do You Yahoo!? >Sign up for SBC Yahoo! Dial - First Month Free >http://sbc.yahoo.com > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Stuff, things, and much much more. http://thinkgeek.com/sf _______________________________________________ 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
