Re: [htdig] A couple of questions about htdig

[Gilles D. <gr...@sc...>]

According to Jim Pye:
>     I've seen earlier versions of this product work and I
> think it is a great piece of software. Now I am trying to
> make it work for me and I have a couple of questions. I am
> loading htdig-3.1.6-2.

I'm not familiar with 3.1.6-2.  I assume this is a package of some sort
built around the 3.1.6 release.  The question is, what other changes have
been made to this "-2" package?  Where did you get it, and are the changes
explained?

>     I get the following error on trying to do a simple
> search after installing on a Solaris 2.8 box. Htdig compiled
> and appeared to load ok.  My system url was http://system/
> which correlated to on the Sun box to /export/home/data/w3.
> 
> 
> ht://Dig error
> 
> htsearch detected an error. Please report this to the
> webmaster of this site. The error message is:
> 
> Unable to read configuration file

I just added http://www.htdig.org/FAQ.html#q5.32 to explain this error.
Please have a look.

>     htdig was loaded to /export/home/data/w3/htdig.  I did
> notice one problem with the installation was that the
> cgi-bin & htdocs placement did not work correctly and it
> went to the default of /opt/www/cgi-bin instead of
> /export/home/data/w3/cgi-bin. Of course htsearch is located
> there.  Can anyone give me some insight on what the problem
> could be if it is not the location of cgi-bin.

The location of cgi-bin only affects the path written into the inital
search.html form, and where the htsearch binary is installed.  You can
easily change these after the fact, as long as the two agree with each
other.  Given that htsearch is actually running, and giving you an
error page, it's not a problem with your cgi-bin.  Instead, I'd be
asking myself if there's a problem with what htsearch thinks CONFIG_DIR
should be.  If you changed the directory for your config files after the
fact, htsearch won't know about this change.

>     One other observation is that when I execute "rundig" on
> a path with only three files for processing, it will run the
> first part very quickly (seconds)  but when it executes
> htnotify that process will suck up all memory (size 515mb
> and resident 150mb) on the system and run for about 20-30
> minutes. This is a Sunblade 100 with 256mb of memory.  Is
> this normal or should I be making some adjustments
> somewhere?

Definitely not normal.  I've never heard of any such problems in htnotify
before.  This brings me back to my first question: what other changes have
been made to this package.  If it's really vanilla 3.1.6, then there may
be a build error on your system causing htnotify to act up.  It might
be useful to run htnotify under the debugger, and interrupt it while
it's sucking up memory to find out where it's executing when it does this.

-- 
Gilles R. Detillieux              E-mail: <gr...@sc...>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/
Dept. Physiology, U. of Manitoba  Winnipeg, MB  R3E 3J7  (Canada)