Ok, there was no response so far - merging the latest state for Zesty Release.
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/312269 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/427775 Title: ntpdate.dhcp always ignored Status in ntp package in Ubuntu: Triaged Status in ntp source package in Trusty: Won't Fix Status in ntp package in Debian: Fix Released Bug description: Ubuntu 9.04, affects the ntpdate binary package Problem: Using dhcp a file ntpdate.dhcp is created but never used. By default NTPDATE_USE_NTP_CONF in /etc/default/ntpdate is set to "yes". This has the following consequences: /usr/sbin/ntpdate-debian parses /etc/default/ntpdate and checks for /etc/ntp.conf.dhcp /etc/ntp.conf /etc/openntpd/ntpd.conf if NTPDATE_USE_NTP_CONF is set to yes. By default ntpd is not installed therefore there is no /etc/ntp.conf.dhcp /etc/ntp.conf or /etc/openntpd/ntpd.conf. ntpdate-debian then defaults to the NTPSERVERS set in /etc/default/ntpdate, namely "ntp.ubuntu.com". Only if NTPDATE_USE_NTP_CONF is set to "no" there will be a check for /etc/default/ntpdate.dhcp and consequently the server supplied by dhcp be used. I propose to set NTPDATE_USE_NTP_CONF to "no" by default. If ntpd is installed, this will override the use of ntpdate and /etc/ntpd.conf.dhcp and /etc/default/ntpdate.dhcp will both be created by DHCP anyway, therefore both packages will use the DHCP supplied servers in any case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/427775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
