http://bugzilla.novell.com/show_bug.cgi?id=557836 http://bugzilla.novell.com/show_bug.cgi?id=557836#c shuang qiu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sqiu@novell.com AssignedTo|bnc-team-screening@forge.pr |werner@novell.com |ovo.novell.com | Severity|Critical |Normal -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=557836 http://bugzilla.novell.com/show_bug.cgi?id=557836#c3 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mt@novell.com |tambet@novell.com --- Comment #3 from Marius Tomaschewski 2009-11-27 16:14:10 UTC --- (In reply to comment #0)

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.

http://bugzilla.novell.com/show_bug.cgi?id=557836 http://bugzilla.novell.com/show_bug.cgi?id=557836#c5 Tambet Ingo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #5 from Tambet Ingo 2009-11-30 09:21:59 UTC --- NetworkManager is dynamic, so when using it, that should be taken into consideration. For example, the nfs dispatcher script we ship does not (and can not!) make much sense. A network connection isn't necessarily THE network connection. So that's why the nfs dispatcher script doesn't even attempt to mount any network file systems - there's simply no information available on the system that ties mounts to networks. The dispatcher scripts however get all the information about network status, including connection's UUID, name, IP information etc. So it would be pretty easy to determine what configuration to use depending on active network (network file systems, printers, firewall, ....). The problem is, we don't have a UI tool to configure any of this. As for this bug's summary, that also works as designed - it's generally impossible to execute "network deactivated" scripts before the connection is deactivated because in many cases (wifi disconnect due to weak signal, ethernet cable pulled out) it's just not known ahead of time (and no, having two sets of "network deactivated" scripts isn't a step in the right direction). (There are other problems with running user scripts before device deactivation as well.) So that leaves only the "soft" NFS mount option. Which sort of makes sense to me - if network configuration is dynamic, so should be the used network services... I'm going to close this bug as WONTFIX because it is not possible to guarantee that network deactivation scripts always get run before network devices get deactivated. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=557836 http://bugzilla.novell.com/show_bug.cgi?id=557836#c7 Rainer Klier changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rainer.klier@gmx.at --- Comment #7 from Rainer Klier 2009-12-17 18:47:56 UTC --- i made a workaround for this problem, at least for smbfs/cifs shares. look at bug #487190 comment #7. i just removed the /sbin/chkconfig, and this did the trick for me. now i have smbfs/cifs-shares even with networkmanager. -- 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.