With all respect for the good work that's gone into NetworkManager, I have to agree with Brian. Every other package that provides a dhclient script is potentially affected by this problem and may or may not be able to provide an equivalent NetworkManager dispatch script. A quick check of the affected packages in Jaunty gives:
$ apt-file -x search 'etc/dhcp3/(enter|exit)-hooks.d' | sed -e 's_:.*__' | sort -u avahi-autoipd dhcp3-client ebox-network ntp ntpdate resolvconf samba-common sendmail-base whereami At least some of these are going to fail to work with NetworkManager. For one example of that, see https://bugs.launchpad.net/ubuntu/+source/whereami/+bug/486406 . And of course that doesn't even address all of the custom dhclient hook scripts developed by sysadmins, such as in the original report here, all of which will break with NetworkManager. Anyone who runs into this problem and searches for a solution pretty quickly encounters the workaround mentioned in #16. It appears to be widely used. Is that how we want people to be operating, by applying someone's workaround script that they find on the net? And at the same time, doesn't it suggest that there should be a straightforward fix? Thanks for your work on NetworkManager. Andrew. -- NetworkManager does not use dhclient-exit-hooks.d https://bugs.launchpad.net/bugs/293139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
