On Fri, 2012-06-08 at 21:43 +0400, Michael Tokarev wrote: > On 08.06.2012 08:43, Ian Kent wrote: > > On Thu, 2012-06-07 at 22:52 +0400, Michael Tokarev wrote: > [] > >> No. fstype=nfs4 is already set, the fix to stop automount > >> from trying to contact portmapper is to specify port= mount > >> option. > > > > It looks like your mistaken, or I have another mistake somewhere. > > > > sun_mount: parse(sun): mounting root /misc, mountpoint test, what > > gnome:/data, fstype nfs, options vers=4 > > mount_mount: mount(nfs): root=/misc name=test what=gnome:/data, > > fstype=nfs, options=vers=4 > > --------^ > > which is not fstype=nfs4 and, as I mentioned already, automount doesn't > > look at the mount options at the moment so it doesn't know the request > > is v4 only. > > Oh. Indeed. You're right. When using -fstype=nfs4 it works. So one > can use either fstype=nfs4 or port=2049, either way it works fine without > the portmapper running on the server. That's wonderful! Yep, the idea being that the "fstype=nfs4" says don't use port name service lookup and is the option that is supposed to be used. But I thought people might also have nfs running on a different port so the "port=" check was added and that should also work. > > Thank you for your patience. np. > > /mjt > -- > To unsubscribe from this list: send the line "unsubscribe autofs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe autofs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
