ntpdate 1:4.2.2.p4+dfsg-1ubuntu2 has a flawed configuration file.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GST |
Fix Released
|
Medium
|
|||
ntp (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
system-tools-backends (Debian) |
Fix Released
|
Unknown
|
|||
system-tools-backends (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
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.
Changed in ntp: | |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
Changed in system-tools-backends (Debian): | |
status: | Unknown → Confirmed |
Changed in gst: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
Changed in system-tools-backends (Debian): | |
status: | Confirmed → Fix Released |
-s is set in /etc/network/ if-up.d/ ntpdate, isn't it?
Not sure about 82774 too, AFAIK edgy doesn't use ntpdate-debian, just plain ntpdate.