Public bug reported:
Restarting NTP more than once at the same time leaves ntpd in a broken
state where it will not set system time but is still running.
Now the ntpdate package stops ntpd, runs ntpdate, then restarts ntpd everytime
an interface mentioned in /etc/network/interfaces comes up via
/etc/network/if-up.d/ntpdate
pm-utils restarts ntpd on every resume from a suspend to reset system
clock to the correct time by restarting ntpd via /usr/lib/pm-
utils/sleep.d/90clock
This happens at the same time (or mostly at the same time) and makes
ntpd being in a broken state.
To solve this issue I can imagin several solutions:
* one of these packages does not restart ntpd anymore
* introduce some sort of central instance that has to be triggered to do the
job tha keeps track of not doing it more often than needed
* introduce some locking mechanism in the ntp init script
what do you think?
-Marc
** Affects: ntp (Ubuntu)
Importance: Undecided
Status: New
** Affects: pm-utils (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ntp (Ubuntu)
Importance: Undecided
Status: New
--
conflict between pm-utils's sleep.d/90clock and ntpdate's if-up.d/ntpdate
https://bugs.launchpad.net/bugs/226125
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
