https://bugzilla.novell.com/show_bug.cgi?id=679059
https://bugzilla.novell.com/show_bug.cgi?id=679059#c2
noel carneiro
Just to make sure I understand correctly:
The fix that solves the problem is to set Defaultvers=3 in /etc/nfsmount.conf Yes, that is what I've done. I've also changed /etc/init.d/nfs from .. mount_usr() .. mount -o nolock $where || { # maybe network device hasn't appeared yet. udevadm settle mount -o nolock $where ..
to .. mount_usr() .. mount -o nolock, vers=3 $where || { # maybe network device hasn't appeared yet. udevadm settle mount -o nolock, vers=3 $where .. according to your suggestions in Bug#623307. It's been working without problems since.
and the root problem is that you are using network manager so the network doesn't get configured until after the init scripts run, and they won't complete until an NFS mount succeeds, and the NFS mount cannot succeed until network managers starts.
If I've got that right, the correct solution might be to tell yast to not allow NFS mounts to be configured if network manager is in use. They really are incompatible.
I really don't know how to configure Yast to do that
If you use network manager, then you should use automounts for NFS.
I have very little experience with automount.
Please confirm this agrees with your understanding.
-- 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.