On Jan 10, 2006, at 7:44 AM, roberto.franchi wrote:
1) when I run the first time rundigg -vvv the system retried a lot of
page from alias (manual of apache) and in main web (generic under
htdocs) but not the virtual site (directory below); after I've changed
the parameter in htdig.conf the process is very quickly and just a
page for each site (index.html) is returned (showing just the site
name without ref:) and if I click on it the referred page is open; I
cannot retrive others pages under each site (.html and .php),
documents (word format e pdf format) inserted for testing the
installation.
Not sure I understand the problem, but here are some things to try
rundig is a shell script and probably has htdig.org defined as a
default web site. try "rundig -c /path/to/your/conf.conf -vvv" to get
it to index your sites and not the defaults in the shell script (or
with the htdig defaults - sorry for the lack of clarity, it's a little
late).
You might also make sure you have backslashes ("\") at the end of each
line of a single option in the config file.
start_url:
http://extranet2.unità.azienda.it
http://intranet2.unità.azienda.it
http://test2.unità.azienda.it
http://test1.unità.azienda.it
should be
start_url:
http://extranet2.unità.azienda.it \
http://intranet2.unità.azienda.it
http://test2.unità.azienda.it \
http://test1.unità.azienda.it
2) how I can creare different search engine for each site? This is for
me important to avoid more argument will be mixed inside the company.
I've found some papers around the web (and in your site) where is
specified to create more .conf file and different database but not un
instruction is given (also in official manual).
There is a paper to explain how to proceed?
How I can with a single htDig installation address htsearch on
different database?
There are many ways to do what you want to do. I think you need a
different .conf file for each site. If the only things that changes
between sites are the URL and the location (names) of the databases,
you can create a common.conf file and include it at the end of of each
site-specific config file.
common.conf contains options that are common among all web sites.
extranet2.conf would contain two lines:
start_url: http://extranet2.unità.azienda.it
database_dir: /var/lib/htdig/db/extranet2
Then, in the URL of each request, you need to tell htdig which conf
file to use by setting the URL parameter "config" so that it might look
like this:
http://extranet2.unità.azienda.it/cgi-bin/htsearch?
words="virtual%20hots%20and%20htdig"&config=extranet2
(the ".conf" is optional in the parameter)
Another possibility is to use the "restrict" URL parameter and set it
to the domain of the current site (so that all site indexes live in the
same database - you're just filtering the results).
Both approaches have their pros and cons. I'd go into more detail, but
a little worn out right now. Good luck.
Ted Stresen-Reuter
http://www.tedmasterweb.com
http://www.clevernet.biz
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
ht://Dig general mailing list: <htdig-general@lists.sourceforge.net>
ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-general
