According to Pub Litics:
> Now, you mention 5.31 on attributes.   And you ask if I have exhausted
> all possibilities there.  I am not excatly sure what is meant by that
> (yes, I have read and studied the FAQ, to the best of my ability).

What I mean is, when you go to http://www.htdig.org/FAQ.html#q5.31,
the answer to question 5.31 lists 8 fairly common reasons why a
configuration attribute setting might seem to be ignored by the program.
We've already ruled out #3, as you only have one config file, and nos. 2,
7 and 8 don't apply to exclude_urls in htdig.  So, that leaves 1, 3, 4,
5 and 6 as possibilities to explore and rule out.  Until you've ruled out
all 8 as possible causes of an attribute not being taken as you set it,
you haven't exhausted all possibilities.  As Geoff pointed out in his
reply, your exclude_urls setting below doesn't have the proper backslashes
at the end of each but the last line, as the last sentence in point #5
of question 5.31 recommends, so this is a likely possibility to explore.

> So, I list, below, what I think you mean as "attributes" from the
> htdig.conf file:
> 
> exclude_urls:         /cgi-bin/ .cgi
>                               /forum/
>                               /applets/
>                               /chat/
>                               /dig/
>                               /htdig/
>                               /poll/
>                               /random/
> 
> Would that indicate that I have "exhausted" the attributes or is there
> something else I need to do in that regard?

This would suggest that you haven't exhausted all possibilities, as
point #5 in 5.31 seems to apply here.  I never said anything about
exhausting the attributes.

> 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
> something you would need to do or tell me to do?  A patch or string
> of some kind?

This was intended as a note to myself and the other developers, pointing
out a need for a code change that seems to have arisen as a result of a
change introduced in 3.1.6.

The part that was intended for you was to look for db.log in your database
directory, and remove it if you want to make htdig restart indexing from
scratch.

-- 
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: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