We've been reviewing the entire Ubuntu delta for ntp, and came across
this sed rule change which is still active. I will drop it for Xenial.
I agree with Jeffrey. The sed rule is incorrect - it does not achieve
what it attempts to achieve, and creates surprising behaviour.
Fundamentally we have
The following patch fixes the problem by *not* replacing ntp servers
with an address beginning with 127.
No, it doesn't. It masks the problem by removing only servers with a
name or address that starts with something other than a '1', followed by
something other than a '2', followed by
This bug was fixed in the package ntp - 1:4.2.4p8+dfsg-1ubuntu4
---
ntp (1:4.2.4p8+dfsg-1ubuntu4) maverick; urgency=low
* debian/dhcp.ntp: Dont remove *all* ntp server from ntp.conf.
(LP: #575458)
* debian/apparmor-profile: Allow access to /dev/ttyS*
(LP: #596859)
--
Thanks this will be fixed in maverick and possibly backported to lucid.
REgards
chuck
** Changed in: ntp (Ubuntu)
Importance: Undecided = Medium
** Changed in: ntp (Ubuntu)
Status: New = Confirmed
--
/etc/dhcp3/dhclient-exit-hooks.d/ntp breaks local NTP server (patch)
Great. Thanks!
--
/etc/dhcp3/dhclient-exit-hooks.d/ntp breaks local NTP server (patch)
https://bugs.launchpad.net/bugs/575458
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in ubuntu.
--
Ubuntu-server-bugs mailing list