Re: [htdig] upgrade to apache 2

[Jim C. <li...@yg...>]

On Thursday, June 5, 2003, at 07:50 AM, Tony Grant wrote:

> htdig.conf works, client1.conf and client2.conf don't.
>
> I believe that htsearch can't find the config files. And I still can't
> figure why.

The path to the directory containing the configuration files is 
hard-coded into htsearch. If it can find one of them, then it should be 
able to find all of them, assuming of course that the ownership and 
permissions are the same for each. You are using just one copy of 
htsearch and have all three config files located in the same directory?

Have you double checked the search pages for the other domains to 
ensure that the 'config' attributes are set correctly (i.e. 
value="client1" and value="client2").

Is there any chance that you have more than one copy of htsearch on the 
server, and that a different version is being picked up for the other 
domains.?

Those are the only things that I can think of to check at the moment. 
The htsearch code is simply trying to read a file with a full name that 
includes the compiled in path, plus the search page's 'config' 
attribute, plus a '.conf'. If it fails to read the file, either the 
path is wrong (e.g. more than one instance of htsearch, misplaced 
config file, incorrect 'config' attribute, etc.) or the file is 
unreadable (e.g. permission and/or ownership problems).

> Everything else works on the server (tomcat, webaliser) which leaves me
> with a much lower opinion of htdig now...

Though I won't go as far as ruling out an ht://Dig problem, the fact 
that things work from the command line implies that the problem is 99% 
likely to be due server configuration issues rather than the ht://Dig 
code. This is especially true if your are using 3.1.6, which has 
received extensive testing. I certainly have no problems using that 
version with Apache 2 on the servers that I maintain.