Thanks Otis. While NFS, dist, sdist and rsync are not available, ssh, sftp and scp are (my previous post --see "Lucene newbie needs advice"-- with ASCII art failed to mention that it's a W2K environment, there's some intentional hiding of this fact, I would much rather be in a *NIX environment). ssh, et.al is provided by Cygwin, so I might venture the task of setting up the aforementioned utils too, but much more important things ahead.
*** New question *** I have noted that Lucene fails to interpret numerous HTML entities, specifically entities in the 82xx range, i.e. — (en-dash) and many others. Now this may not be a Lucene issue, I'm looking at the code as I post, but I'm curious to its origins and why they don't seem to be parsed properly in the index. Tim > -----Original Message----- > From: Otis Gospodnetic [mailto:[EMAIL PROTECTED]] > Sent: Friday, August 30, 2002 10:55 > To: Lucene Users List > Subject: Re: Lucene newbie needs advice > > > Sharing a read-only index is not a problem, as long as both machines > running Tomcat can access it. That is, you would have to > NFS-mount the > disk/partition with the index. > > Or you can use something like dist or sdist with rsync to > send a single > index from the machine where you create and update your index, to all > the Tomcat machines that need to read it when people perform searches. > > Otis > > > --- "Stone, Timothy" <[EMAIL PROTECTED]> wrote: > > Lucene users, > > > > Lucene looks like the answer to my site-only searches, a robust API > > and > > active user community. I have a rather static informational site, > > html and > > some pdf, coming online; hits may be heavy in the > beginning, but drop > > dramaticly following opening. > > > > The general practice of searching the web is known, but search > > engines and > > the technology/terminology of searching are foreign to me and I'm > > looking > > for a rapid, drop in solution, with little customizing at this stage > > (until > > I can come up to speed). I'll be running an Apache Tomcat > environment > > (really only to enable Luncene). > > > > How much harm is there in deploying the Lucene demo/example, with > > some "look > > and feel" changes and handling for possible redirects to alternate > > web > > search engines? > > > > Also, can multiple Tomcat servers running the Lucene demo share a > > single > > index? Are there threading issues to be concerned about? > > > > My hardware is rather robust at this point. I have two IBM Web > > servers with > > dual 2Ghz XEON processors, 2Gb RAM and dual Gb NICs. The future has > > these > > servers in roles as load balancing proxies in front of a switch, or > > switches, managing dedicated web hardware. This is what I'm working > > with; > > capital expenditures are spent. > > > > My configuration plan looks something like this: > > > > > > Box 1 > > > > +--+........>+--+ > > | Apache1 | | > > |__| |_Tomcat1 +-+ > > | Apache2 | | +-+ shared lucene index > > | | | Tomcat2 > > +--+........>+--+ > > > > > > Box 2 > > > > +--+........>+--+ > > | Apache3 | | > > |__| |_Tomcat3 +-+ > > | Apache4 | | +-+ shared lucene index > > | | | Tomcat4 > > +--+ .......>+--+ > > > > > > > > Thanks, > > Tim > > > > *************************************************** > > Timothy Stone | Sun Certified Java Programmer * > > Web Master | tstone at cityofhbg dot com * > > * City of Harrisburg | 717.255.7297 > > * Pennsylvania USA | 717.903.9162 > > *************************************************** > > "This Satan's drink [coffee] is so delicious, > > we shall cheat Satan and baptize it." > > Pope Clement VIII > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Finance - Get real-time stock quotes > http://finance.yahoo.com > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
