|
On Sun, Oct 03, 1999 at 06:46:04PM -0400, James CE Johnson wrote:
[snip]
>If I fire up htdig, it needs to know where to connect to to build it's
>index files. I want to run it inside the cluster of course. If I tell
>it to look at http://foo.bar.com from any node in the cluster, it gets a
>'connection refused'. If I tell it to look at node01.foo.bar.com, then
>all is well but the URLs it builds are all http://node01.foo.bar.com
>which do no good for folks outside of the cluster looking at search
>results.
I'm not sure this is a good solution, or even if it'll work, but
what if you add an entry in /etc/hosts of the digging box to point
the ip of node01 to the name foo.bar.com. node01 shouldn't really
need to ever need to get to foo.bar.com for real, since it's name
is services01.foo.bar.com from inside the cluster, right?
felix
--
felix sheng ... felix@xxxxxxxxxx
PGP: <http://wwwkeys.us.pgp.net:11371/pks/lookup?op=get&search=0x2CA84A01>
----------------------------------------------------------------------
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
|
