Hi, Shams.  It seems you had some trouble replying to my last couple
messages, as you sent two replies to my earlier message, and three to
my last one (so I got 4 copies of one, and 6 of this last one, because
they came to me directly and via the list).  Be aware that replies to the
list don't always come back to you right away - they are often delayed
by several minutes, so you should wait before reposting.

According to [EMAIL PROTECTED]:
> Thanks Gilles, thats cleared a lot of queries up for me... I didn't
> know that htDig 3.2... was installed as part of Red Hat 7.3.
> 
> You're right, the standard Apache httpd.conf does define the cgi-bin
> as "/var/www/cgi-bin/", however my supervisor had set everything up
> to the old format of "/home/httpd/html/cgi-bin".  And the ScriptAlias
> definition was changed to reflect this.

I figured that may have been the case, but I mentioned it just in case
you were going under an assumption about the default installation that
wasn't reflected in the current defaults.  The old cgi-bin was actually
/home/httpd/cgi-bin, though.  No matter, as long as it works for you.

> >How do you know that?  If you have two installations of ht://Dig, how
> >do you determine which htsearch binary is the correct one, let alone
> >determining which of the two binaries is actually being run by the server?
> >Did you track down, based on your Apache configuration, exactly which
> >htsearch the server will run, and did you run that particular htsearch
> >binary to get it's version number?  E.g.  "/var/www/cgi-bin/htsearch -\?"
> 
> I can't check back because I have wiped everything and reinstalled Red
> Hat.  But thinking back, the second (3.1.6) installation of htDig was
> within my webserver (/home/httpd/html) and the 3.1.6 htsearch was placed
> in the /home/httpd/html/cgi-bin/ dir.  I believed that I was calling
> the correct htsearch because the Apache configuration was looking at
> the correct cgi-bin dir. and this was reflected in search.html.

Sounds right to me.  You probably had built a database with your 3.1.6
installation, and that's what htsearch from the web server was searching.
But when you subsequently ran htdig and htsearch from the command line,
you were running the 3.2.0b4-011302 binaries which built and searched a
different database, hence the different htsearch results on the command
line vs from the web server.

> how do you check the version of a particular htsearch binary ?
> 
> I tried "htsearch -?" , but it simply brings up a list of possible
> options that can be run with htsearch (e.g. -v, -c, etc).

Yes, and just before the list of options, about on the 3rd line of output,
it shows the version number.  See also http://www.htdig.org/FAQ.html#q5.33

> Anyway, i'm about to try and re-intsall htDig 3.1.6.
> 
> thanks again, your help was much appreciated,

Good luck to you.  If you install just the one version, it should no longer
be driving you crazy.

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


-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
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