>>>>> Sergio Gelato <sergio.gel...@astro.su.se> writes:
> According to the man page for auto.master(5) you can use the
> "nosymlink" option to prevent bind mounting of local NFS filesystems.
Do I understand it correctly that this option, being listed in
auto.master(5), will affect all the mounts within a “map”?
> Furthermore, if your /etc/hosts has a 127.0.1.1 line with your
> hostname in it, or if you use x=127 for values of (y, z, t) other
> than (0, 0, 1), it may be that automount misses the fact that the NFS
> filesystem is local. I consider this to be a bug, however, and would
> advise against relying on it. The "nosymlink" mount option is safer.
ACK, thanks.
The strange thing is that I'm pretty sure I also have got a
suggestion to use the port= NFS mount option to prevent a bind
mount, but don't seem to see it anywhere in this bug report.
To note is that the suggestion appears to work. Specifically, I
now use port=2049 (following $ rpcinfo -p | grep -F -- nfs.) As
per nfs(5), I'd expect port=0 also to work, but it fails like:
# mount -v -o ro,nosuid,nodev,soft,nolock,rsize=8192,wsize=8192,port=0 \
-- 127.0.0.1:/home/public /mnt/
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Tue Sep 11 00:09:02 2012
mount.nfs: trying text-based options
'soft,nolock,rsize=8192,wsize=8192,port=0,vers=4,addr=127.0.0.1,clientaddr=127.0.0.1'
mount.nfs: mount(2): No such file or directory
mount.nfs: trying text-based options
'soft,nolock,rsize=8192,wsize=8192,port=0,addr=127.0.0.1'
mount.nfs: an incorrect mount option was specified
#
Still, I believe that either implementing a separate option to
avoid “binding” a single mount, or documenting the work-around
above, is necessary.
TIA.
--
FSF associate member #7257 http://sfd.am-1.org/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
