[pkg-ntp-maintainers] Bug#788014: does not start at bootup

Elliott Mitchell ehem+debian at m5p.com
Tue Dec 22 05:36:29 UTC 2015


I was able to recreate this without systemd.  In my case all it took was
to have a network interface that took a long time to configure/come up.
I'm unsure it is the best way to do it, it currently configures a switch
chip attached to an interface when the interface comes up.  This appears
to have had the effect of slowing down `ntpdate` which ended up hanging
around long enough to interfere with `ntpd`.

Since the new default configuration for `ntpd` is to allow extreme clock
changes on start that obviates the need for `ntpdate` on the device and
so I simply purged `ntpdate`.

Encouraging the removal of `ntpdate` may be the best solution to #788014.
There is a needed to be a notice to people that ntpd's -g option is now
the default and needs to be disabled if one has reliable system clocks.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         EHeM+sigmsg at m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445



More information about the pkg-ntp-maintainers mailing list