"Fadi Mansour" <[EMAIL PROTECTED]> writes:
> I have a little problem concerning wwwoffle and ht-dig, I'm not sure
> what the problem is, but I have a theory. The problem started when for
> no apparent reason, htdig failed to index my wwwoffle cache. Sometimes
> htdig would succeed and others it won't. And then after some time (I
> didn't have much time to dive into the problem) htdig no longer was able
> to build the index.
>
> Looking at the log:
>
> New server: al-berkeh, 8080
> 0:0:0:http://al-berkeh:8080/search/start4.html: ++ size = 584
> 1:1:1:http://al-berkeh:8080/search/start3.html: + size = 497
> 2:2:1:http://al-berkeh:8080/search/index/: +++ size = 167
> 3:3:2:http://al-berkeh:8080/search/start2.html: + size = 497
> 4:4:2:http://al-berkeh:8080/search/index/http/: not found
> 5:5:2:http://al-berkeh:8080/search/index/ftp/:
> +++++++++++++++++++++++++++++++++
> ++++++++++++++++++++++++++++++++++++++ size = 2539
> 6:6:2:http://al-berkeh:8080/search/index/finger/: size = 100
>
> As you can see it seems that htdig couldn't find the
> 'search/index/http/'.
> So it seems there's no reason why htdig would say 'not found', but
> there's a catch. The list is long, and it might take some time for the
> computer (with a Cyrix 100MHz processor) to deliver it. Could a timeout
> be the cause of the problem? If so, can this timeout be changed?
It is possible that the timeout set in the htdig configuration file is
the problem. The default value for htdig is a timeout of 30 seconds.
The configuration files that come with WWWOFFLE have a timeout of 300
seconds specified in them. I would be surprised if it really took 5
minutes to generate the index.
You can increase the timeout by editing the htdig-full.conf and
htdig-incr.conf files which are in
/var/spool/wwwoffle/search/htdig/conf/.
--
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop [EMAIL PROTECTED]
http://www.gedanken.demon.co.uk/
WWWOFFLE users page:
http://www.gedanken.demon.co.uk/wwwoffle/version-2.7/user.html
