OK, I originally had it listed below, exactly as follows:

exclude_urls:           /cgi-bin .cgi
                        /forum
                        /applets
                        /chat
                        /dig
                        /htdig
                        /poll
                        /random


That is when I noticed the multifarious, repititious searching and index problem.  So, 
in an attempt to fix it, I amended the file, as follows:

exclude_urls:           /cgi-bin/ .cgi
                        /forum/
                        /applets/
                        /chat/
                        /dig/
                        /htdig/
                        /poll/
                        /random/

However, I received the same results, either way.  

Not sure what you mean by I need "\" at the end of the line.  If I might, could I ask 
that you kindly illustrate this for me, possibly using my example, above?  

Do you mean like this:

exclude_urls:           /cgi-bin \ .cgi \
                        /forum \
                        /applets \
                        /chat \
                        /dig \
                        /htdig \
                        /poll \
                        /random \

As to the second part of the question, again, not sure what you mean "have I 
interrupted" htdig.  Here is what I do.  I index the site, going into cd www cd htdig 
cd bin.  I then type perl rundig.  It takes a few moments.  No interruptions.  I then 
exit.  I then use the program, as do others, from the browser.  I, then, re-index 
maybe a week or so later following the same procedure.  Does this adequately answer 
the question?  No, when it is indexing in Telnet I do not interrupt it for any reason. 
 I just let it run its cycle.

Thanks.  Hope we are getting closer!




--

On Fri, 11 Oct 2002 15:57:18  
 Geoff Hutchison wrote:
>On Fri, 11 Oct 2002, Pub Litics wrote:
>
>> exclude_urls:                /cgi-bin/ .cgi
>>                              /forum/
>>                              /applets/
>>                              /chat/
>>                              /dig/
>>                              /htdig/
>>                              /poll/
>>                              /random/
>
>Do you have them listed in your config file exactly like this? If so,
>you're missing the "continue on next line" bits--basically you need a
>"\" character at the end of the line (nothing at all after) for the next
>line to be considered part of the attribute.
>
>Alternatively, you can read in the contents of a file:
>exclude_urls: `/path/to/exclude.txt`
>
>http://www.htdig.org/confindex.html
>http://www.htdig.org/cf_variables.html
>
>> >persistent, because if it's there, htdig reads it and if you interrupt
>> >htdig again, it recreates it again.  So, if you interrupted htdig before
>
>So this is the next question. When you index, have you interrupted htdig
>and restarted?
>
>> OK, next (assuming that "attributes" have been "exhausted") you say
>> that "we need to get htdig to issue a warning."  I assume that this is
>
>
>
>--
>-Geoff Hutchison
>Williams Students Online
>http://wso.williams.edu/
>
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>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
>


____________________________________________________________
Get 25MB of email storage with Lycos Mail Plus!
Sign up today -- http://www.mail.lycos.com/brandPage.shtml?pageId=plus 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
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

Reply via email to