On Friday 22 January 2010 10:58:27 Tim wrote:
> On Thu, 2010-01-21 at 19:09 -0500, Neal Becker wrote:
> > It is not supported for a Grid Engine installation that the local
> > hostname contains the hostname "localhost" and/or the IP address
> > "127.0.x.x" of the loopback interface.
> > The "localhost" hostname should be reserved for the loopback interface
> > ("127.0.0.1") and the real hostname should be assigned to one of the
> > physical or logical network interfaces of this machine.
>
> Conflicting advice, and the first lot is just plain weird.
What is the conflicting advice in there? The OP had modified the localhost
line in /etc/hosts and added the machine hostname there (as the second field):
On Friday 22 January 2010 00:09:49 Neal Becker wrote:
> /etc/hosts says:
> 127.0.0.1 nbecker6 localhost.localdomain localhost
^^^^^^^^
So his real hostname, "nbecker6", resolves to 127.0.0.1, which is unsupported
by the Grid Engine (and probably some other apps AFAIK). Furthermore,
"localhost" became an alias for "nbecker6", which is also unsupported. I'm
even surprised that the Grid Engine didn't complain about "nbecker6" not being
a FQDN...
Instead, the hostname "nbecker6" should resolve to some other IP associated to
one of his network interfaces, while *only* the "localhost" hostname should
resolve to 127.0.0.1 (and not be an alias for something else for that matter).
It is a very sane advice, AFAICS.
> It's about time the advice in the hosts file was changed from telling
> you not to change the following line (which has often, ALREADY, been
> badly mangled, but the person reading this is unaware) to telling you
> precisely what the first two lines should be.
That's probably a good idea, the warning about that line should be as explicit
as possible (do not remove, do not modify, if you see that it has been
modified by someone else correct it, etc...).
> Though, to be honest, I'm surprised that the TCP/IP stack isn't designed
> to presume those addresses, already, without requiring entry into the
> hosts file. Other systems work that way. Is there any situation where
> you don't want those addresses to be interpreted like that?
I believe it is a matter of some userspace apps also depending on that line,
not just TCP/IP stack. So removing the file altogether will not work. And
honoring the settings inside is also mandatory. All in all, no easy way out of
the problem. :-)
Best, :-)
Marko
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
