According to Jim Cole: > On Friday, November 15, 2002, at 05:15 AM, shams khan wrote: > > I have a couple of questions relating to creating multiple indexes / > > databases. > > � > > 1) When creating a second index, I obviously change the "prefix" path > > (so that all the files get installed to a different directory), but I > > keep the IMAGE_DIR the same (as I am not too bothered about images > > being overwitten)..... but what about the BIN_DIR.� Can i overwrite > > the binaries from the first htdig install with binaries from the > > second ?� My concern is that other variables set in the CONFIG file > > gets hard coded into the binaries... i fthis is the case then I will > > need to set the BIN_DIR to different folders for seperate HtDig > > installations... ?? > > I am not sure that you gain much by setting up separate directories for > the binaries. You can always explicitly specify the config file to be > used. But other than wasted disk space and additional maintenance, I > don't suppose it hurts anything.
This sounds like a lot of bother for nothing. The only need for separate binaries would be so you can configure separate values of CONFIG_DIR for each. So, the only binary for which you'd need to install multiple copies would be htsearch. If you try to set up multiple copies of htdig, htmerge, etc., then you're likely going to run into some problems unless you're very careful to isolate them each to their own separate BIN_DIR. This shouldn't be necessary as you can safely run one copy of htdig with different config files using the -c option. > > 2) I would like to create 3 seperate databases for 3 different folders > > on our webserver.� I don't want to use 1 database with exclude and > > restrict variables, because I've read in the FAQ that they can be > > overridden! > > � > > So... can someone advise me whether there is any security risk with > > the following indexes / settings: > > It depends on what you mean by security risk. The only reason I see for > multiple htsearch binaries is to prevent one from using another's > config file. However, if you turn around and put all of the binaries in > the same directory with predictable names, I am not sure that you gain > anything. Good point. The only way to protect some config directories is to protect the htsearch binaries that use them. Much of the details of this are discussed in http://www.htdig.org/FAQ.html#q4.20, so don't try to reinvent the wheel until you've very thoroughly read through this section. -- 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: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ 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
