From: Nye Liu <nyet@mrv.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "autofs@linux.kernel.org" <autofs@linux.kernel.org>,
Ian Kent <raven@themaw.net>
Subject: Re: "Use bind instead of nfs if host is localhost" feature is broken? removed?
Date: Tue, 15 Mar 2011 21:33:10 -0700 [thread overview]
Message-ID: <4D803D86.6000805@mrv.com> (raw)
In-Reply-To: <4D7FF5D2.3080107@zytor.com>
On 3/15/2011 4:27 PM, H. Peter Anvin wrote:
> On 03/12/2011 05:32 PM, Ian Kent wrote:
>> On Thu, 2011-03-10 at 15:59 -0800, Nye Liu wrote:
>>> I have been relying on the behavior that
>>>
>>> foo host:/export/foo
>>>
>>> uses 'bind' if host is localhost, and 'nfs' otherwise...
>>>
>>> i.e. if i am on the machine "host", /export/foo is mounted on /mnt/foo using
>>> bind, but if i am not on "host", host:/export/foo is mounted on /mnt/foo
>>> using nfs.
>>>
>>> But the latest version of autofs no longer does that.
>>
>> What latest version?
>>
>
> I believe this is related to a change in the network layer in Linux,
> which breaks the localhost test not just for autofs but for almost any
> application which uses the same, portable technique for determining the
> localness of a host address.
Indeed. /etc/hosts had "127.0.0.1 host", and not the "real" ip matching dns.
I changed /etc/hosts from 127.0.0.1 to its real ip, and autofs now
properly detects that "host" is local and uses bind now, as it should. I
verified this has nothing to do with autofs version and more to do with
kernel revision.
2.6.32 "works", 2.6.37 is "broken".
next prev parent reply other threads:[~2011-03-16 4:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 23:59 "Use bind instead of nfs if host is localhost" feature is broken? removed? Nye Liu
2011-03-13 1:32 ` Ian Kent
2011-03-15 23:27 ` H. Peter Anvin
2011-03-16 4:33 ` Nye Liu [this message]
2011-03-16 22:42 ` Nye Liu
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=4D803D86.6000805@mrv.com \
--to=nyet@mrv.com \
--cc=autofs@linux.kernel.org \
--cc=hpa@zytor.com \
--cc=raven@themaw.net \
/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.