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
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/288905
Title:
/etc/init.d/ntp doesnt use ntpdate to ensure clocks are aligned before
starting server.
Status in ntp package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: ntp
Ubuntu: 8.04.1
ntp: 1:4.2.4p4+dfsg-3ubuntu2
Despite other comments on here that ntpdate should be run from ifup
scripts there is still a fundamental issue.
If due to failures such as #114505 not bringing up ntpd correctly if
the clock drifts you have to ifdown, ifup an interface. On a major
server thats just plain ridiculous...To fix the ntp daemon I have to
pull down an ENTIRE network interface and stuff every service that is
running on that interface - simply to fix ntpd.
The alternative is that I have to either recognise and issue and then
/etc/int.d/ntp stop
ntpdate-debian
/etc/init.d/ntp start
again silly - because an /etc/init.d/ntp restart should work - the
point of running NTP is it syncs.
Therefore I propose that the /etc/init.d/ntp script is patched to
include running of 'ntpdate-debian' during startup of the ntp server.
This is a far more fail-safe method of working instead of forcing the
admin to have to remember to run ntpdate-debian in case the clock has
drifted excessively.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/288905/+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
