at least in unstable, recompiling the package with --with-libtirpc got me up and running again. i have a host that had both IPv4 and IPv6 addresses on its interface. in a fit of address reclamation, i had removed the IPv4 address, and that broke the automounter. the NFS server i use for home is IP'd and DNS'd for v4 and v6.
essentially, after pulling down source and build-deps [along with libtirpc-dev], doing this: cd autofs* sed -i 's#--with-sasl#--with-sasl \\\n\t\t--with-libtirpc#g' debian/rules fakeroot debian/rules binary got me up and running again. until some steps are taken here or there in the build process of autofs, i guess i'll have to have this package pushed via puppet, so that my IPv6 only machines can still have NFS automounted home. david On Sat, 12 Apr 2014 18:16:19 +0000 Ivan Shmakov <i...@siamics.net> wrote: > >>>>> Arne Nordmark <nordm...@mech.kth.se> writes: > > >> It looks like this is down to autofs not handling names using only > >> IPv6 addresses. Not sure why this happens given that I would have > >> expected it to just pass this directly to mount(8) but it's > >> presumably doing more than that. Not sure exactly what the cause > >> is, though /usr/lib/x86_64-linux-gnu/autofs/mount_nfs.so is using > >> getaddrinfo and I can't see any obvious defect with a quick glance > >> over the sources. > > > Autofs does some initial NFS probing of its own, as part of handling > > server replication. > > JFTR, I’d rather look for some clean way of /disabling/ such > probing altogether, preferably as a per-share option. My > NFSv4/IPv6 servers aren’t currently replicated anyway, and such > a work-around would’ve solved this problem at least for me. > > […] > > -- > FSF associate member #7257 > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
