I respect the package maintainers decision to let this one slide but the
comment in /etc/default/ntpdate is confusing. You shouldn't have to read
the code to figure out that if /etc/ntp.conf doesn't exist that a
different NTP server will be used. Thanks for the clarification via
Launchpad.
--
Marking won't fix as the comment is good enough IMO.
** Changed in: server-papercuts
Status: Triaged = Won't Fix
** Changed in: ntp (Ubuntu)
Status: Triaged = Won't Fix
--
Confusing comments in /etc/default/ntpdate
https://bugs.launchpad.net/bugs/537451
You received this bug
** Changed in: server-papercuts
Milestone: maverick-alpha-3 = maverick-beta
--
Confusing comments in /etc/default/ntpdate
https://bugs.launchpad.net/bugs/537451
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in ubuntu.
--
** Changed in: server-papercuts
Importance: Undecided = Low
** Changed in: server-papercuts
Status: New = Triaged
** Changed in: server-papercuts
Milestone: None = maverick-alpha-3
--
Confusing comments in /etc/default/ntpdate
https://bugs.launchpad.net/bugs/537451
You received
** Changed in: server-papercuts
Assignee: (unassigned) = Dave Walker (davewalker)
--
Confusing comments in /etc/default/ntpdate
https://bugs.launchpad.net/bugs/537451
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in ubuntu.
--
You're right. The comments in /etc/default/ntpdate are confusing.
** Summary changed:
- ntpdate-debian not syncing time
+ Confusing comments in /etc/default/ntpdate
** Changed in: ntp (Ubuntu)
Importance: Low = Wishlist
** Changed in: ntp (Ubuntu)
Status: Incomplete = Triaged
--
