https://bugzilla.novell.com/show_bug.cgi?id=341647
User tambet@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=341647#c13
Tambet Ingo changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED
--- Comment #13 from Tambet Ingo 2009-03-23 00:50:27 MST ---
First of all, when you use NetworkManager, you can forget about
/etc/sysconfig/network/* configuration files. NM has it's own (cross distro)
system which doesn't match in many places with suse configuration, so it was
decided it's easier for everybody if the answer is "no", rather than "depends".
For re-mounting services not listed in /etc/fstab, you'll need to write a
dispatcher script for it yourself. The current dispatcher script is generic
with a single rule: "when a device is activated, mount all NFS services". That
doesn't take account movable devices (like laptops) where you can get connected
anywhere and thus might not have access to the network resources (like NFS,
..) of your home/office. NM provides a way to solve that (by giving extra
information to the dispatcher scripts), but there are currently no tools that
use it. The rules ideally need to be like "if a specific configuration is
activated/deactivated, do ...", which requires user configuration and right
now, there are no graphical tools to configure that.
A comment for "a brief blip or reconnect *to the same network* causes nfs
mounts to be destroyed" - The dispatcher script runs right after disconnect -
at which point, there is no way of knowing whether you'll get a connection back
(to the same network or not) right away, so it's working as designed.
In summary, I'm going to close this bug again - I don't think it would be a
good default to try to remount NFS services which do not appear in /etc/fstab.
I don't think it's what most people would want and we have infrastructure to
override that.
--
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.
