I can confirm this is working in maverick. Manually skewing the date,
restarting and checking the date reports the current date/time. It's
been fixed somewhere in the cycle, so marking Fix Released.
** Changed in: ntp (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: server-paper
** Changed in: server-papercuts
Assignee: (unassigned) => Dave Walker (davewalker)
--
Date not updated by ntp when network interfaces started
https://bugs.launchpad.net/bugs/567701
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp i
** Changed in: server-papercuts
Importance: Undecided => Medium
** Changed in: server-papercuts
Status: New => Triaged
** Changed in: server-papercuts
Milestone: None => maverick-alpha-2
--
Date not updated by ntp when network interfaces started
https://bugs.launchpad.net/bugs/567
Just to note, this appears to be working out of the box with current
Maverick packages for me, there appears to be quite a few changes to NTP
packaging as well.
--
Date not updated by ntp when network interfaces started
https://bugs.launchpad.net/bugs/567701
You received this bug notification bec
Yes, that's not working out of the box.
** Changed in: ntp (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: ntp (Ubuntu)
Status: New => Confirmed
** Also affects: server-papercuts
Importance: Undecided
Status: New
--
Date not updated by ntp when network interfaces
** Patch added: "etc-default-ntpdate-use-default-server.patch"
http://launchpadlibrarian.net/44939981/etc-default-ntpdate-use-default-server.patch
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/44939529/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
h
