According to [EMAIL PROTECTED]:
> i'm using Red Hat Linux 7.3....... running htsearch from command prompt,
> i use "htsearch -c htdigs.conf" and i run it from where htdigs.conf
> is located (which is /home/httpd/html/htdig/conf/)
>
> typing "which htsearch" gives me:
>
> /usr/bin/htsearch
>
> looking at the dir /usr/bin, i notice that all the programs (htdig,
> htdump, htload, etc) are in there... so i guess that they were put
> there as part of the htDig installation.
>
> I clearly have two installations of htDig which must be confused.
Yes, it seems you've installed your ht://Dig package using the prefix
of /home/httpd/html/htdig, so the binaries in /usr/bin are more than
likely part of the htdig-3.2.0-2.011302.i386.rpm package that ships
with Red Hat 7.3.
> My search.html is definatly using/calling the correct htsearch in
> the /cgi-bin folder.
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 -\?"
> And /cgi-bin has correctly been defined as
> /home/httpd/html/cgi-bin within the Apache httpd.conf.
That strikes me as odd. The standard Apache httpd.conf from Red Hat 7.3
defines cgi-bin as:
ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"
so I'd think that a form with action="/cgi-bin/htsearch" would run
/var/www/cgi-bin/htsearch on a "vanilla" Red Hat 7.3 installation.
If you've installed the htdig-web-3.2.0-2.011302.i386.rpm package,
then you're running a 3.2 beta of htsearch. Did you change this
ScriptAlias definition in httpd.conf?
> Anyway, I've decided to wipe everything and re-install Linux (as i'm
> only using a test machine). Thanks for the help in pointing me in
> the right direction, though I can't seem to fix the problem.
>
> To ensure that I don't make the same mistakes second time round
> on a fresh install of HtDig, can someone tell me whether my
> assumptions/thinking below is correct (so that I can understand HtDig
> better):
>
> - in the first CONFIG file, what is the purpose of defining the variable
> exec_prefix when it is equal to prefix (the root dir tree) ?
The exec_prefix variable is a holdover from earlier 3.1.x releases, where
it was used for setting BIN_DIR. As of 3.1.6, BIN_DIR is set directly
by the ./configure script. You no longer need to worry about it if using
3.1.6.
> - why does htdig install copies of the binaries in /usr/bin ?
That's where Red Hat decided to put them in their RPM package. The
Linux file system standards recommend that for standard system packages
(of which htdig is one in Red Hat 7), binaries go in /usr/bin.
When you install your own packages from sources, you're not bound by
those standards, so you can put them wherever you prefer.
My recommendation is not to install the Red Hat RPM packages for htdig,
because they're a bit buggy, but instead install only the stable 3.1.6
release, either from scratch or from the RPM packages in
http://www.htdig.org/files/binaries/
(Note that these RPM packages also follow Linux filesystem standards
to some extent.)
> - once I have made changes to the CONFIG file and then Compile and
> Install HtDig (using "make" and then "make install".... am I right in
> thinking that whenever I run htsearch/rundig/etc, it somehow looks
> back at the original installation directory for the CONFIG file to
> find the values for DATABASE_DIR, COMMON_DIR, etc..... OR.... are those
> values hard coded in the binaries, and are the installation files and
> the CONFIG file are not used again (unless of course I want to install
> HtDig again) ?
No, the values of the Makefile variables in CONFIG get compiled into the
binaries. After a "make install", you can actually remove the original
source directory as the binaries don't use it.
Note that rundig is a shell script, not a binary. It contains shell
variables, set during the "make install", which define certain paths.
If you move things around, you may need to change some of these paths.
> - how would I install another version of htDig? is it as simple
> as changing the CONFIG file to install to a different directory
> (by changing the 'root directory tree'. Can I do this and have
> two seperate htdig installations (with the aim of two seperate
> indexes/search forms/etc). Or do I have to create another set of
> installation files and create a second CONFIG file ?
You can create more than one installation of ht://Dig from one single
source tree, by changing CONFIG, recompiling, and doing another
"make install". It's not necessary to unpack the source and start
over from scratch. However, when wierdness happens, it may be a good
idea to start from the beginning just to make sure you haven't missed
a step somewhere.
But, you don't necessarily have to have more than one installation of
the ht://Dig binaries, if your aim is only to have two separate indexes,
search forms, etc. You can do that even with one set of binaries.
See http://www.htdig.org/FAQ.html#q4.2
and http://www.htdig.org/FAQ.html#q4.4
> - if i have created an index using rundig, and I want to re-index a
> specific directory/URL. Which files do I need to delete before I run
> rundig again (after I have chanced the htdig.conf file) ? Is it just
> the db files in /htdig/db.
If you're running the standard "rundig" script that's installed in your
BIN_DIR by "make install", without any modifications, then you don't need
to delete anything. The standard rundig script reindexes from scratch,
by running "htdig -i" and "htmerge". The -i option to htdig tells it to
remove any old database that exists using the same database name as it's
going to use now, so you wind up with a fresh, new database. But, if you
have multiple config files with different settings of database_dir or
database_base, rundig will only remove/regenerate the database selected
by the config file you tell it to use.
That's why with your current setup, you still had an old database lying
around. The htdig-3.2.0-2.011302 package put its database in one location,
while your own 3.1.6 installation used a different location. If you ran
rundig or htdig -i from one of the installations, and htsearch from the
other installation, then htsearch wouldn't give you the results of the
latest run of rundig/htdig.
--
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:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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
