All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valentijn Sessink <valentyn@blub.net>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Kevin Coffman <kwc@citi.umich.edu>,
	Steve Dickson <SteveD@redhat.com>, Jim Rees <rees@umich.edu>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Strange rpc.svcgssd behavior
Date: Wed, 17 Nov 2010 19:52:36 +0100	[thread overview]
Message-ID: <4CE42474.7020604@blub.net> (raw)
In-Reply-To: <6980C086-795B-49EF-8F93-8C49A51E35CF@oracle.com>

Op 17-11-10 18:51, Chuck Lever schreef:
> The hostname is added to localhost entries in /etc/hosts because some
> applications require at least one entry with the local host's
> hostname in /etc/hosts.  When a system comes up with all of its
> network interfaces offline and without any IP addresses assigned,
> what else can be done?

Read /etc/hostname?

Adding "localhost" entries to /etc/hosts does nothing for applications 
that require an entry with the hostname in /etc/hosts, *unless* the 
hostname is "localhost". Now as Networkmanager (apparently) sets the 
hostname to "localhost", I can see why Networkmanager wants to add 
"localhost" to /etc/hosts afterwards. But hey, we might as well set the 
hostname to everyone.loves.networkmanager, then add *that* to /etc/hosts 
and run into problems.

Please note, that /etc/hosts has nothing to do with the hostname, it's 
only a way to statically (and locally) add things to the resolver.
[...]
> for the host is added to /etc/hosts, and then added back to the
> localhost entries when all network interfaces are disabled.

I don't think adding or not adding them to /etc/hosts makes any 
difference. I'd guess that calling sethostname() causes problems.

V.

  reply	other threads:[~2010-11-17 18:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15 17:39 Strange rpc.svcgssd behavior Chuck Lever
2010-11-16 15:58 ` Valentijn Sessink
2010-11-16 19:44   ` Valentijn Sessink
2010-11-16 20:17     ` Jim Rees
2010-11-16 20:22       ` Chuck Lever
2010-11-16 20:54         ` Jim Rees
2010-11-16 21:41           ` J. Bruce Fields
2010-11-16 21:42           ` Chuck Lever
2010-11-17 15:18             ` Steve Dickson
2010-11-17 15:30               ` Chuck Lever
2010-11-17 15:54                 ` Kevin Coffman
2010-11-17 16:05                   ` Chuck Lever
2010-11-17 16:26                     ` Kevin Coffman
2010-11-17 17:51                       ` Chuck Lever
2010-11-17 18:52                         ` Valentijn Sessink [this message]
2010-11-17 16:15                   ` Valentijn Sessink

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CE42474.7020604@blub.net \
    --to=valentyn@blub.net \
    --cc=SteveD@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=kwc@citi.umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rees@umich.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.