Author: andi
Email: [EMAIL PROTECTED]
Message:
I did several tests on different machines with a smaller set of tables (about 30.000
entries).
First of all, the search.cgi seems to be the fastest - of course. The PHP-solution is
slower.
I noticed some differences between Apache and AOLserver,
i'm indexing my state government's web sites. however,
there are some sites that indexer just stalls on. See
the last line below:
...
Indexer[22838]: [1]
http://www.doer.state.mn.us/lr-mlea/artcl-30.htm
Indexer[22838]: [1]
http://www.doer.state.mn.us/lr-mlea/artcl-31.htm
Indexer[22838]: [1]
Cheers,
To be able to index most of file formats, you need to have each parser. But as suffix
has never been the file format proof, I created for Unix (Windows?) systems this
parsing gateway.
It is not yet finished, but works pretty well for now.
This udm-gw PERL program can also be used for
Author: mocha
Email: [EMAIL PROTECTED]
Message:
i just tried running only one indexer and after about 30 minutes, it stalled. i
attached gdb to the PID and here is what it shows:
(gdb) bt
#0 0x1604946a8 in select () at select:2
#1 0x120014664 in UdmHTTPGet (Indexer=0x120177000,
Oh !
My mistake, the hint to add in the indexer.conf to ask udm-gw to deal with this
program.
I also left the AddType lines. Use AddType Regex if udmsearch 3.1.
Sorry
AddType text/plain \.pl$ \.js$ \.txt$ \.h$ \.c$ \.pm$ \.e$
AddType text/html \.asp$ \.cfm$ \.cgi$
From your TODO list:
"Make a script which can display found document with search words
highlighted."
See an example here:
http://arcadeathome.efront.com/search/index.php?ps=10t=q=mameps=20m=and;
o=0ul=arcadeathome.efront.com%2F
If you click on the (Highlight) link, you will see the keywords
