http://bugzilla.novell.com/show_bug.cgi?id=557836
http://bugzilla.novell.com/show_bug.cgi?id=557836#c3
Marius Tomaschewski
2. I use Network manager to manage my network connection, not sure it happens with traditional ifup.
The behaviour is correct -- it will not work as it is configured. As Werner already described, there are two network scripts involved. The start order is: /etc/init.d/network -- requires only local-fs, sets up _ifup_ interfaces supported for $remote_fs (=nfs) /etc/init.d/nfs -- requires $network (network), mounts nfs; that is, implements/provides $remote_fs /etc/init.d/network-remotefs -- requires $remote_fs, starts NetworkManager The stop order is: network-remotefs, nfs, network When ifup is in use, /etc/init.d/nfs will work over normal ethernet, bridge, bonding, vlan interfaces, but not over wlan, ppp, tunnels... You can not mount via /etc/init.d/nfs and use NetworkManager. The NetworkManager can not be started via network script, because it requires $remote_fs -- it is installed on /usr that maybe on nfs. To mount nfs when NetworkManager is in use, it is required to disable nfs using "insserv -r /etc/init.d/nfs" and start it (mount) via NM dispatcher, that is via /etc/NetworkManager/dispatcher.d ... AFAIS, there is a nfs dispatcher script -- but it expects enabled nfs; this looks like it will not work... same with the autofs dispatcher... It also restarts/stops with every interface up/down... A mechanism like "man 5 ifservices" for ifup would be required here... NM issue => Tambet. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.