desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #14512
[Bug 83604] Re: ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
** Changed in: system-tools-backends (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-tools-backends in Ubuntu.
https://bugs.launchpad.net/bugs/83604
Title:
ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
Status in The Gnome System Tools:
Fix Released
Status in “ntp” package in Ubuntu:
Fix Released
Status in “system-tools-backends” package in Ubuntu:
Fix Released
Status in “system-tools-backends” package in Debian:
Fix Released
Bug description:
Binary package hint: ntp
This is in feisty (but it is an explanation for bug #82774 as well,
the basic reason is the same for edgy, different configuration flaws).
I just noticed the problem in a feisty up-to-date system. In ntpdate
(1:4.2.2.p4+dfsg-1ubuntu2) packaging, /etc/default/ntpdate is set up
in such a way that it defaults to the ntp servers defined in
/etc/ntp.conf, an empty file; which makes debconf to *not* create a
proper /etc/ntp.conf if one decided to install ntpd on a whim. And to
add insult to injury, /etc/default/ntpdate does not have the needed
config flag to have ntpdate log its success or failure to the syslog
("-s"), thus it defaults to standard output, which upstart diligently
makes all efforts to send to /dev/null.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gst/+bug/83604/+subscriptions