On Thu, 24 Feb 2005, Dan Langille wrote:
On 24 Feb 2005 at 13:29, Jim wrote:
On Thu, 24 Feb 2005, Georgina Allbrook wrote:
Searching around for a reason why htsearch was not doing what it should I looked at the datestamp for the htsearch binary. It has not been updated since the re-install. I removed htsearch and re-installed and it is now working as expected.
For future reference, the path to the config directory is compiled into htsearch for reasons having to do with security. When there is a need to change the location of config files, htsearch should be recompiled with the new path.
So how does the above relate to the -c option on htsearch?
# htsearch -? htsearch: invalid option -- ? usage: htsearch [-v][-d][-c configfile] [query_string] This program is part of ht://Dig 3.2.0b4-011302
The -c option will override the compiled-in path, but only from the command line. This is useful for testing and perhaps for scripting local, command line based searches, but it is not applicable to calling htsearch through HTTP. There are ways to get around this restriction, but they
involve either writing wrappers or intentionally bypassing the security
features built into htsearch when compiling the program.
Jim
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ ht://Dig general mailing list: <[email protected]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
