On 03.06.2012 23:38, Jamie Heilman wrote: [] >> 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.
Please stop shouting - I based my analysis/suggestions on some assumptions and actually even asked if that's the case. Note I didn't downgrade the bug severity, awaiting your comments/confirmation. >> 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. If you want fighting, you're ofcourse free to rebuild anything, but I don't think it is productive. You now demonstrated your usage case and that is enough to convince me or anyone else that I took a wrong way, and the issue is quite a bit more complex. Note again that NFSv4 does not work with autofs still -- namely, its /net map still requires portmapper. And note - also again - that even without turning on this "HAVE_NFS" thing, it were working just by a chance. I'll take another look at what the two options (with and without "NFS Support") gives. But I want to understand: why all this shouting from you? Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
