According to Budd, S.:
> > I am using htdig 3.1.1
> >
> > If the configuration file has a name with a .(dot) in it ( other than
> > for the file name extension .conf then it is not
> > recognized when it is used in the search form.
> > The configuration file is not found.
> >
> > eg
> > if the configuration file name is dig-a.conf
> > and the form has <input type=hidden name=config value="dig-a">
> > then it will find the configuration file.
> >
> > but if the configuration file name is dig.a.conf
> > and the form has <input type=hidden name=config value="dig.a">
> >
> > the result is the error message
> > Unable to read configuration file
> > '/home1/www-data/htdig-3.1.1/conf/htdig.conf'
> >
> > It looks like the following line ( no 144 ) in htsearch strips out the
> > dots.
> > configFile << '/' << input["config"] << ".conf";
No, the problem is the test on line 130, which ignores the user-specified
config input parameter if it has a dot in it. A while back, someone
proposed changing it to:
&& !strstr(input["config"], "./"))
but that change never made it in. Give that a try to see if it fixes
your problem. (Note: change BOTH the function name and the 2nd argument.)
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
