FWIW, this issue is still present in older releases. Effectively, if NTP
is installed and configured to access X ntp server and timesyncd would
still try to fallback to ntp.ubuntu.com.
In proxied environments, this will result in ntp.ubuntu.com being
unavailable.
** Also affects: ntp (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: ntp (Ubuntu Xenial)
Importance: Undecided
Status: New
--
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/1597909
Title:
systemd-timesyncd unit still running after installation of ntp package
Status in ntp package in Ubuntu:
Fix Released
Status in ntp source package in Xenial:
Incomplete
Status in ntp source package in Zesty:
Incomplete
Bug description:
I recently installed the ntp package on a fairly vanilla installed-
from-DVD Xenial system, and noticed that after the package
installation both systemd-timesyncd and ntp were running:
# systemctl status ntp systemd-timesyncd.service --no-pager
ntp.service - LSB: Start NTP daemon
Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
Active: active (running) since Tue 2016-06-28 19:21:16 HDT; 6min ago
Docs: man:systemd-sysv-generator(8)
CGroup: /system.slice/ntp.service
3364 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 112:118
[...log lines...]
systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
`-disable-with-time-daemon.conf
Active: active (running) since Sun 2016-06-26 06:53:05 HDT; 2 days ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 821 (systemd-timesyn)
Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
CGroup: /system.slice/systemd-timesyncd.service
821 /lib/systemd/systemd-timesyncd
[...log lines...]
I was able to do "systemctl stop systemd-timesyncd.service" manually
without any trouble, but presumably if I hadn't noticed the situation
I might have had problems with the two services both running
simultaneously until my next reboot.
(Once the systemd-timesyncd service is stopped, it is prevented from
starting again by the constraint in the disable-with-time-daemon.conf
file.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1597909/+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
