"Use bind instead of nfs if host is localhost" feature is broken? removed?
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.
Do i have to use this everywhere now?
foo (1),host(2):/export/foo
The behavior is more like what I expect, but it seems wasteful.
Signature · 7 lines
Nye Liu [email protected] (818) 772-6235x248 (818) 772-0576 fax "Who would be stupid enough to quote a fictitious character?" -- Don Quixote
Ian Kent
maintainerQuoted 11 lines · Nye Liu
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/foousing bind, but if i am not on "host", host:/export/foo is mounted on/mnt/foousing nfs.But the latest version of autofs no longer does that.
What latest version?
Quoted 7 lines
Do i have to use this everywhere now?
foo (1),host(2):/export/foo
The behavior is more like what I expect, but it seems wasteful.
Quoted 7 lines · Ian Kent
Quoted 6 lines · Nye Liu
I have been relying on the behavior that
foo host:/export/foo
uses 'bind' if host is localhost, and 'nfs' otherwise...
Quoted 8 lines
Quoted 5 lines
i.e. if i am on the machine "host", /export/foo is mounted on
/mnt/foousing bind, but if i am not on "host", host:/export/foo is mounted on/mnt/foousing 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.
-hpa
Quoted 14 lines · H. Peter Anvin
Quoted 13 lines · Ian Kent
Quoted 11 lines · Nye Liu
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/foousing bind, but if i am not on "host", host:/export/foo is mounted on/mnt/foousing nfs.But the latest version of autofs no longer does that.
Quoted 7 lines
Quoted 2 lines
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".
Quoted 14 lines · H. Peter Anvin
Quoted 13 lines · Ian Kent
Quoted 11 lines · Nye Liu
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/foousing bind, but if i am not on "host", host:/export/foo is mounted on/mnt/foousing nfs.But the latest version of autofs no longer does that.
Quoted 7 lines
Quoted 2 lines
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".