Subject: Re: [htdig] 3.1.5 update drama
From: N Irons (firstname.lastname@example.org)
Date: Thu Mar 23 2000 - 09:58:36 PST
On 3/23/2000 at 9:57 AM, email@example.com (Adam Rice) wrote:
> If you need the -c option to make htsearch work on the commandline,
> then you'll probably need an
> <input type=hidden name=config value=whatever>
> in your search form
Yeah, that's covered. I've got three databases, and three search forms,
so the configs have been specified in the HTML forms since rollout.
3.1.2 worked great, and the only things which I've changed are the paths
for conf & common (in the configuration step) and the database directory
(in the config file). All three are where they're supposed to be -- to
make sure, I renamed the config file, generated the "htsearch can't find
the config file" error from the web, copied the path it suggested, and
fed it directly to htsearch with -c. After I restored the proper name
of the config file, it worked fine.
I only get the no-data response from htsearch via the web when
everything, including htsearch via the shell, seems fine. When there's
an obvious problem (like not being able to find conf or common),
htsearch via the web returns diagnostic errors as expected.
To unsubscribe from the htdig mailing list, send a message to
You will receive a message to confirm this.
This archive was generated by hypermail 2b28 : Thu Mar 23 2000 - 08:54:47 PST