Yeah stupid me, I found out now.

Maybe insert a "parsing config file" message before starting the parse ?

Thanks !

ht://dig Start Time: Sat Dec  7 12:49:27 2002
parse error
In line 160

3.2.0b4-20021201 seems to crawl all right nevertheless ...
This means that the config file parser found a problem on line 160 of your config file.
(I'm not sure how easy it will be to improve this message, I think it comes from the yacc program code that generates the config file parser code.)

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

--
Franck Horlaville,

Technical Director - Athena Online s.a.
Web site creation and hosting
--
<http://www.athena.online.co.ma/>


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