The stale file was apparently left by /etc/dhcp/dhclient-exit- hooks.d/ntp. Since this dhclient script updates the ntp.conf.dhcp file when a new NTP server is advertised via DHCP, it should be OK to always use the most recent file between /var/lib/ntp/ntp.conf.dhcp and /etc/ntp.conf.
The attached patch changes the initscript to use /var/lib/ntp/ntp.conf.dhcp only if it is newer than /etc/ntp.conf. ** Patch added: "Only use /var/lib/ntp/ntp.conf.dhcp if it is newer than /etc/ntp.conf" https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1472056/+attachment/4425385/+files/ntp-dont-use-stale-dhcp-conf.patch ** Bug watch added: Debian Bug tracker #600661 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600661 ** Also affects: ntp (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600661 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472056 Title: ntpd can use stale /var/lib/ntp/ntp.conf.dhcp config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1472056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
