Subject: Re: [htdig] Re: [ANNOUNCE] ht://Dig 3.1.4 RPMs for Red Hat
Date: Thu Dec 16 1999 - 12:23:08 PST
On Mon, 13 Dec 1999, Gilles Detillieux wrote:
> According to Hugo.van.der.Kooij@caiw.nl:
> > On Mon, 13 Dec 1999, Gilles Detillieux wrote:
> > > According to Hugo.van.der.Kooij@caiw.nl:
> > > > On Fri, 10 Dec 1999, Geoff Hutchison wrote:
> > > > > At 12:17 AM +0100 12/11/99, Hugo.van.der.Kooij@caiw.nl wrote:
> > > > > >Did you add the funny stuff at the end /etc/htdig/htdig.conf?
> > > > >
> > > > > What "funny stuff" are you referring to?
> > > >
> > > > a few lines like:
> > > > local_urls: http://192.168.1.1/=/home/httpd/html/
> > > > start_url: http://192.168.1.1/
> > > >
> > > > > >It took me while to find out that two lines of start_url results in random
> > > > > >behaviour.
> > > > >
> > > > > If you mean trying to split start_url over multiple lines, you need
> > > > > to include a '\' at the end. Otherwise it will only read the first
> > > > > line and ignore the rest.
> > > >
> > > > Nope. I mean two times a line called start_url: with one at the usual
> > > > place and one at the bottom.
> > >
> > > There's nothing wrong with having two definitions of start_url (or any
> > > other attribute) in one config file. The second will simply override
> > > the first definition. It will do this consistenly. Do you have any
> > > specific details on the sort of "random behaviour" you claim this caused?
> > > Does the random behaviour disappear when you remove or comment out the
> > > first start_url definitions? It may be that the problem is with the IP
> > > address that was pulled out of your httpd.conf.
> > After disabling the extra lines and correctly stating what should be there
> > on the first few lines it worked as should be.
> OK, but that's not what I asked. I wanted to know if disabling the
> FIRST start_url definition made any difference to your results, because
> you claimed that having two separate definitions of start_url led to
> "random behaviour". I'd still like to know what that random behaviour is,
> and how having two separate definitions of an attribute can lead to it.
The machine runs production now so testing is not possible. (I got
it solved after spending an afternoon on it.) As said I had to clear out
all that was added and then some more and move it to the top of the config
> On the other hand, if the "random behaviour" is in fact just htdig diging
> a site other than what you wanted, because the RPM grabbed an address from
> your httpd.conf other than what you wanted, then this is a configuration
> issue and not a bug in htdig. That's what I'm trying to sort out here.
It was htdig not digging at all. Just a glance and it was gone. The result
were not logical at all.
-- Hugo van der Kooij; Oranje Nassaustraat 16; 3155 VJ Maasland firstname.lastname@example.org http://home.kabelfoon.nl/~hvdkooij/ -------------------------------------------------------------- Use of any of my email addresses for unsollicited (commercial) email is a clear intrusion of my privacy and illegal!
------------------------------------ To unsubscribe from the htdig mailing list, send a message to email@example.com You will receive a message to confirm this.
This archive was generated by hypermail 2b28 : Thu Dec 16 1999 - 12:41:17 PST