If ntpd is running, ntpdate should never run - doing so causes clock
jumps. In Trusty, /etc/network/if-up.d/ntpdate actually stops ntpd so
ntpdate can run. Debian jessie doesn't do this, so if this was from
upstream, it's been fixed.
>From /etc/network/if-up.d/ntpdate:
-----
if [ -e /usr/sbin/openntpd ]; then
service='openntpd'
else
service='ntp'
fi
invoke-rc.d --quiet $service stop >/dev/null 2>&1 || true
/usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null || :
invoke-rc.d --quiet $service start >/dev/null 2>&1 || true
------
Workaround:
sudo mkdir /etc/network/if-up.d.disabled
sudo dpkg-divert --divert /etc/network/if-up.d.disabled/ntpdate --rename
/etc/network/if-up.d/ntpdate
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1278359
Title:
ntpdate call frequency
Status in ntp package in Ubuntu:
Confirmed
Bug description:
Currently ntpdate is started every time the network interface changes to up.
On systems that have a hardware clock this is not nessesary, causeing
unnessesary traffic and load on ntp servers.
If easily possible ntpdate shold rather be called daily or weekly via
cron, if there is a hardware clock present.
(affects all Ubuntu versions)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1278359/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
