On 03.06.2012 16:31, Jamie Heilman wrote: > Package: autofs > Version: 5.0.6-2 > Severity: important > > For reasons I haven't entirely taken the time to figure out, the > changes between 5.0.6-1 and 5.0.6-2 have destroyed my ability to > automount NFSv4 shares. My configs are dead simple, my entire > auto.master is simply: "/home /etc/auto.home" and /etc/auto.home > contains: "jamie -vers=4 canarsie:/home/jamie" > > After upgrading to 5.0.6-2 automount never gets as far as exec'ing the > mount command; the most immediately obvious difference from 5.0.6-1 is > that it appears to attempt to communicate to the portmapper on > canarsie (my nfs server) and fails (understandbly---I'm running NFSv4 > only, no portmapper listening externally, nor is it necessary).
This is interesting. Autofs package has native support for NFS from the ground up, but apparently this support has never been activated in debian package, because autofs configure script checks for presence of /sbin/mount.nfs to decide whenever to compile in NFS support and uses stubs it mount.nfs hasn't been found. But on buildds that file doesn't exist. In 5.0.6-2, I explicitly told configure that we do have mount.nfs, so NFS support has been activated, whatever it means. I'm running 5.0.6-2 version currently, and it is definitely able to mount nfs4 shares - I've an NFS4 server right here which IS used with automount. But please take a look at the configuration (/etc/default/autofs) -- for example, there's MOUNT_NFS_DEFAULT_PROTOCOL setting which might help. Does it work if you enable portmapper/rpcbind on the server? (It is enabled here) Thank you! /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
