> The culprit seems to be in how ntpdate-debian is programmed. the logic ignores /var/lib/ntpdate/default.dhcp if /etc/default/ntpdate sets NTPDATE_USE_NTP_CONF=yes (the default).
This matches my understanding when I looked at ntpdate-debian with a similar issue, though I haven't tried to verify this for certain. I wonder what the intention of ntpdate-debian is in this case. Does it do what it does because we don't want NTP to be set from DHCP by default? Is the reason you're facing this problem because your hardware doesn't have an RTC, or because system doesn't use the RTC at boot time, and is stuck at epoch? Fixing NTP from DHCP should certainly fix the issue, but why isn't the RTC being set correctly at install time and read correctly at boot time? I recently had a case where I fixed this in the kernel, and then the NTP DHCP situation didn't matter. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1257082 Title: MAAS does not use NTP servers specified in DHCPD options To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1257082/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
