Your message dated Tue, 18 Sep 2018 11:27:35 +0200
with message-id <[email protected]>
and subject line Closing ntpdate ifupdown related bugs, removed from Buster
has caused the Debian Bug report #714997,
regarding ntpdate gets invoked by default
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
714997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714997
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ntpdate
Version: 1:4.2.6.p5+dfsg-2
Severity: normal
If I install the ntpdate package, in order to have the useful diagnostic
tool of the ntpdate(8) program, an if-up script also gets installed, which
uses ntpdate in order to adjust the system clock every time a network
interface comes up. Sure that's a vaguely sensible way to use ntpdate,
but wanting to do that is not inherent in installing the ntpdate program.
I think there should be two distinct packages here: one providing the
ntpdate program (and ntpdate-debian), and a second one implementing
the specific use of ntpdate to repeatedly adjust the system clock.
The package descriptions must reflect these distinct purposes. If for
some reason you're not willing to split the packages, then the secondary
purpose of the single package needs to be stated in its description.
(The present description of the ntpdate package describes the ntpdate
program, but makes no mention of running it automatically.)
-zefram
--- End Message ---
--- Begin Message ---
Version: 1:4.2.8p12+dfsg-2
Dear user,
the bug you have submitted is related to the ifupdown triggers shipped
by the ntpdate package that did a one-shot time sync every time an
interface managed by ifupdown was configured.
The hooks have been removed from the ntpdate package in version
1:4.2.8p12+dfsg-2, which will be part of the Buster release.
ntpdate.NEWS reads:
TL;DR: The ntpdate package does NOT ship triggers for ifupdown to run
a one-time sync every time an interface comes up anymore. These hooks
will also be removed on upgrades to Buster. It is strongly recommended
to switch to a permanent NTP daemon like ntp, systemd-timesyncd or chrony.
If you need a one-time sync in your setup please arrange for it
yourselves, i.e. by calling sntp with the appropriate parameters in
/etc/network/interfaces(.d) .
Historically the package ntpdate has included both /usr/bin/ntpdate
(which is
the historic go-to program for one-shot NTP querying) and ifupdown
hooks to
execute a one-shot NTP query on every interface up event.
The ifupdown hooks have introduced buggy behaviour by syncing too often
(on every ifup), too seldom (never again) and are likely to interfere with
other time-keeping measures on the same system including ntpd. The hooks
frequently caused dependency problems with local DNS resolvers or uncommon
network configurations. They have therefor been dropped from the ntpdate
package.
For time synchronisation purpose please use one of the many timekeeping
daemons in Debian (ntp, systemd-timesyncd, chrony).
For the manual use, /usr/bin/ntpdate has been deprecated upstream and
replaced by /usr/bin/sntp (in the sntp binary package). If you want a
proper one-shot sync against a pool of servers you may also consider the
-q option of ntpd.
Best Regards,
The NTP maintainers
--- End Message ---
