https://bugzilla.novell.com/show_bug.cgi?id=855820 https://bugzilla.novell.com/show_bug.cgi?id=855820#c3 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #3 from Neil Brown <nfbrown@suse.com> 2014-01-21 02:22:35 UTC --- The "Enable NFSv4" setting "NFS Settings" in the NFS {Client,Server} Configuration in YAST causes the "rpc.idmapd" daemon to be run, which is needed for NFSv4, but not for v2 or v3. So it really is "enable", not "activate" or "require". Also if it isn't enabled, the NFS server will not export with NFSv4. When you try to mount something it will always use the highest version support by both client and server, unless explicitly requested otherwise. So if you mount from an NFSv4 server without "Enable NFSv4" selected, then it might fail ... though in recent kernels the NFS client doesn't use rpc.idmapd so maybe it will. Yes I appreciate that this is not really ideal. Things keep changing and it is hard to keep up. I hope to substantially revise the NFS startup soon to work properly with systemd. I'll try to make it more seemless when I do that. I'm going to mark this as "FIXED" for now as I think the 30 delay has been address and the other issues are being tracked elsewhere. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.