With this stupid change, network manager doesn't even use the "ntp server" variable sent to it from the dhcp server.
C'mon folks. This is basic, really basic, autoconfiguration functionality. It makes ntp in environements where they don't let machines communicate outside of the network useless, as the hardcoded value in /etc/ntp.conf no longer works in such environments. Sure, I could simply change the value that goes into /etc/ntp.conf but that gets awfully tiresome on a laptop that roams from one network to another and needs a different value for each network. This is *exactly* why DHCP has the ability to give this information to the client. Except that Ubuntu/Canonical, in their infinite wisdom have decided that this use-case is stupid and just neutered it. Not everyone works is wide open Internet environment folks. The sooner you can learn that and remember it when you are making infrastructure- impacting changes, the better your product will be for everyone. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
