*** This bug is a duplicate of bug 238805 ***
https://bugs.launchpad.net/bugs/238805
I replicated this issue in 64-bit ArchLinux. The issue (ntpdate doesn't
synchronise time when year is in far future) is not Ubuntu specific.
--
ntp for amd64 is broken
https://bugs.launchpad.net/bugs/267267
*** This bug is a duplicate of bug 238805 ***
https://bugs.launchpad.net/bugs/238805
Bug entered to NTP bugzilla.
https://support.ntp.org/bugs/show_bug.cgi?id=1061
--
ntp for amd64 is broken
https://bugs.launchpad.net/bugs/267267
You received this bug notification because you are a member
*** This bug is a duplicate of bug 238805 ***
https://bugs.launchpad.net/bugs/238805
I have a problem with ntpdate that cannot fix incorrect time at 64-bit
Ubuntu server, it reports that year 2280 is OK (offset only -0.008843
sec). This has to be a bug in ntpdate/ntpd. (ntpd was running on
*** This bug is a duplicate of bug 238805 ***
https://bugs.launchpad.net/bugs/238805
correct command line for test is this one (ntpdate, not ntp...)
$ ntpdate -v ntp.ubuntu.com; date; uname -a
--
ntp for amd64 is broken
https://bugs.launchpad.net/bugs/267267
You received this bug
*** This bug is a duplicate of bug 238805 ***
https://bugs.launchpad.net/bugs/238805
I fixed time manuly with date and I can see that ntpdate doesn't update
it. So it looks as I see the same issue as described in #238805.
** This bug has been marked a duplicate of bug 238805
ntpd doesn't
*** This bug is a duplicate of bug 238805 ***
https://bugs.launchpad.net/bugs/238805
I am not sure what I observe here, it is more complicated.
1) system time was wrong year 2280, ntpdate cannot fix it (and it reports
offest -0.005494 sec)
2) system time was wrong, year 2009, ntpdate fixed
*** This bug is a duplicate of bug 238805 ***
https://bugs.launchpad.net/bugs/238805
I cannot repeat the same scenario at i686, I cannot set year 2280 at
i686 system.
AMD64:
$ date 110300102280
Wed Nov 3 00:10:00 UTC 2280
$ ntpdate -v ntp.ubuntu.com; date
20 Nov 11:37:01 ntpdate[14368]:
