The way the newer versions solve this is to have a native systemd
service and in there there is:
Conflicts=systemd-timesyncd.service openntpd.service
That ensures only one of these can be started.
Xenial has no systemd service at all, it has sysV and uses the systemd
generator.
So there is no "just add the line" fix available.
Xenial as-is
$ timedatectl status
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
systemctl status systemd-timesyncd.service
● 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 Wed 2018-03-21 16:00:19 UTC; 1min 30s ago
This isn't even fully protected if you install ntp (not chrony) as it
was the ntp server back in Xenial. (Right after install it still runs).
What stops it there for NTPd is that this uses a config dir which pulls in:
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
So any further starts will be blocked:
# don't run timesyncd if we have another NTP daemon installed
ConditionFileIsExecutable=!/usr/sbin/ntpd
ConditionFileIsExecutable=!/usr/sbin/openntpd
ConditionFileIsExecutable=!/usr/sbin/chronyd
ConditionFileIsExecutable=!/usr/sbin/VBoxService
You see that if you check systemd-timesyncd.service:
$ systemctl status systemd-timesyncd.service
● 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: inactive (dead)
Condition: start condition failed at Wed 2018-03-21 16:06:42 UTC; 44s ago
ConditionFileIsExecutable=!/usr/sbin/ntpd was not met
After installing Chrony this is the same:
Condition: start condition failed at Wed 2018-03-21 16:11:37 UTC; 1s ago
ConditionFileIsExecutable=!/usr/sbin/chronyd was not met
That is good (no special issue to chrony) and bad (actually all
timeservers "collide" right after install).
A reboot or restart will pick that up.
OTOH it is discouraged to start/stop/restart other packages services form a
postinst - as the first thought would be to do refresh for that condition after
installing any of these.
Given that there was not a single complaint about it in 2 years of
Xenial other than us now looking for it in detail I'd rate it low, but
it is a valid issue.
** Also affects: ntp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: openntpd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ntp (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: ntp (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: chrony (Ubuntu Bionic)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756987
Title:
chrony install does not stop systemd-timesyncd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1756987/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
