That's what I figured as well but couldn't get it working. I only
accessed the file with pico and have never had line end issues before
with it. I ended up deleting the entire install and installing fresh
and everything seems to be working! Not sure why, I must have messed up
the file somehow.
On Nov 28, 2004, at 7:54 PM, Jim wrote:
> On Sun, 28 Nov 2004, Ian Landsman wrote:
>> I just installed the latest htdig beta 6. I've never used htdig
>> before but everything went fine with the install on RH 8. The only
>> thing is htdig always throws a parse error on the conf file and then
>> just defaults to using the default settings (only crawls htdig.org,
>> etc). It gives a line number but it seems to be useless. I've
>> modified the file, I've even removed part of the file and all of the
>> file and it still just throws an error. Has anyone seen this before?
> Corrupt config files are not unheard of, but the problem is typically
> to something done to the file after it is installed.
> Did you by chance edit it on one machine and copy it to another? If so,
> did you ensure that line breaks were converted (or not) appropriately?
> If you did not copy it between machines, are you certain that you
> the file in a manner that preserved unix style line breaks?
> Have you doubled checked any edits that you made to verify that no
> slipped in? One typo to be especially careful of is adding spaces (or
> other characters) after a line continuation character (i.e. \).
> You might want to check the file with 'cat -v' and look for
> occurrences of
> non-printing characters. If you find any, that is likely the problem.
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real
> Discover which products truly live up to the hype. Start reading now.
> ht://Dig general mailing list: <htdig-general@...>
> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html
> List information (subscribe/unsubscribe, etc.)