Hi, this long dormant bug has been resurrected early last year, but I
think it is time to close it.
There were various discussions in the bug about when to set or drift, but while
all is correct that isn't the scope of the bug.
There are other open that will address e.g. that on a running system you
shouldn't time warp but instead drift, just as comment 6 explains. And I agree
- other than explicitly requested - in a systems lifetime time should only
drift, but not be reset.
But then the request here was about setting time correctly initially (set) and
kept correct later (drift).
That is now done by systemd anyway - see timedatectl for a starter if you are
interested.
That said the bug no more really "applies", due to that.
So it is not fix released but Won't Fix (Alt solution available and being the
default)
** Changed in: ntp (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/288905
Title:
/etc/init.d/ntp doesnt use ntpdate to ensure clocks are aligned before
starting server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/288905/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
