Wouldn't it be better to use inotify on /etc/network and /etc/network/interfaces to have nm-system-settings be notified of any changes in the file? The same would certainly apply to ifcfg for Fedora and SuSE, i.e. /etc/sysconfig/network-scripts for Fedora-based dists. Then the file(s) can just be reloaded, when changed and the need for a daemon restart is gone.
Why is nm-system-settings coupled with NetworkManager (started implicitely), anyway? Why can't nm-system-settings be explicitely started and stopped from the init.d script with e.g. a dbus-message "nm- system-settings-available" and "nm-system-settings-unavailable" to message state between daemons (to avoid races). Even separate init.d scripts would make sense IMO. -- [intrepid] network manager does not stop nm-system-settings when stopped https://bugs.launchpad.net/bugs/293751 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
