Consider replacing ntpdate calls by 'ntpd -g'
Bug #583994 reported by
C de-Avillez
This bug affects 17 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NTP |
Invalid
|
Undecided
|
Unassigned | ||
ntp (Debian) |
New
|
Unknown
|
|||
ntp (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
ubuntu-meta (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: ntp
Given that 'ntpdate' is being obsoleted upstream [1], we should replace 'ntpdate' usage by:
* ntpd -qg (if we really want to set the time and exit), or
* ntpd-g (if we want to keep ntpd running)
the '-q' option will set the clock once, and exit; the 'g' allows for large corrections to the clock, like what is done by 'ntpdate'.
Changed in ntp: | |
status: | Unknown → New |
Changed in ntp: | |
importance: | Unknown → Undecided |
status: | New → Invalid |
Changed in ntp (Ubuntu): | |
status: | Invalid → Confirmed |
milestone: | none → ubuntu-15.02 |
Changed in ntp (Debian): | |
status: | Unknown → New |
Changed in ntp (Ubuntu): | |
milestone: | ubuntu-15.02 → none |
Changed in ubuntu-meta (Ubuntu): | |
milestone: | ubuntu-15.02 → none |
Changed in ntp (Debian): | |
importance: | Unknown → Low |
Changed in ntp (Debian): | |
importance: | Low → Unknown |
To post a comment you must log in.
See also bug 322518. I think we want to get rid of ntpdate, and use ntpd everywhere, which would be more consistent.