Michael Tokarev wrote: > On 03.06.2012 18:39, Michael Tokarev wrote: > > On 03.06.2012 17:31, Michael Tokarev wrote: > > [] > >> Does it work if you enable portmapper/rpcbind on the server? > >> (It is enabled here) > > > > I just verified - and indeed, with no rpcbind running on the > > server, automount does not work anymore, ie, it requires > > portmapper on the server even for NFSv4 mounts. Retitling > > as appropriate. > > And this is indeed the case. The whole logic in autofs around > this is wrong in so many ways I'm afraid to count!.. :( > > For now I suggest to actually run rpcbind on the server, this > issue needs to be dealt with upstream. Neither version of the > code is right.
Hell no. The entire reason I bothered with v4 is because it gets rid of the external portmapper requirement, rpc.statd, rpc.mountd, and rpc.lockd. All of which was working just fine until 5.0.6-2 came along. > Since there's an easy workaround for you, and this issue does > not default settings (you have to explicitly disable rpcbind > on the server for it to stop working), and even more -- it > actually _works_, but with a several-second timeout (at least > here, please reply if it is not the case for you), I downgrade > this bugreport to wishlist severity. Don't assume the server is a Debian system and that you know its defaults, even though it happens to be in this case. Regardless, I'm not going to change my server config to satisfy the new, broken, requirements of this package, I'll rebuild the damned thing myself from here on out if I have to. The sane thing would be to just revert the build instructions until such time the native NFS support in automount correctly supports NFSv4 mounts without needless rpc usage. -- 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
