From: pelicancomputers (rfransix@yahoo.com)
Date: Wed May 22 2002 - 16:57:05 EDT
thank you. everyone said the same thing, and here's a
good answer:
I can concurr - if there is an unexpected network
failure (or someone
starts playing with the 'ifconfig hme0 unplumb'
command) you still get
log files.
the only real reason to have loghost after a public IP
is if you are using a centralized log server (which I
would also recommend for those total system failures)
lastly (but certainly not leastly) I've configured my
systems to pass a single 'hosts' file between multiple
systems, and having 'loghost' under the loopback IP
means not having to recreate the hosts file for each
system.
--- pelicancomputers <rfransix@yahoo.com> wrote:
> i read there is an advantage to having loghost in
> the /etc/hosts file, after 127.0.0.1 loopback entry:
>
> 127.0.0.1 localhost loghost loopback
>
> this prevents logging from stopping if the primary
> interface, where loghost is usually placed, stops
> working.
>
> can you concur? are there other advantages?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:21 EDT