Michael Tokarev wrote: > Overall, the code quality is very very low, I'm not sure > it is possible to maintain this package without very > serious work with upstream first.
I took a stab at a slightly less annoying workaround, and found that with 5.0.6-2 using a map of "jamie -fstype=nfs4 canarsie:/home/jamie" worked too. Reviewing the code, I'm actually kinda surprised it worked, but the more I try to follow the logic, the more fragile everything seems to get. It would appear that what I should be doing if nfs_mount_uses_string_options is true, is setting MOUNT_WAIT to something other than -1 to reproduce the old behavior I was getting. (Also, the MOUNT_WAIT description in /etc/default/autofs is slightly wrong, it mentions umount(8) but that should probably be mount(8).) I'll test that later, and either run this under a debugger or instrument it a little to be sure I understand what's going on, but I think the way automount is handling NFSv4 capability probing is pretty iffy at the moment. I suspect specifying an explicit port= option should be taken into account (I'm not doing that currently but I really should be, and it's entirely arguable that my previous configuration should have failed becuase I wasn't setting the port explicitly). -- Jamie Heilman http://audible.transient.net/~jamie/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
