timesyncd: add Conflicts for ntpd and chronyd

Users might end up with more than one of those service enabled, through
admin mistake, or broken installation scriptlets, or whatever. On my machine,
I had both chronyd and timesyncd happilly running at the same time. If
more than one is enabled, it's better to have just one running. Adding
Conflicts will make the issue more visible in logs too.

diff --git a/units/systemd-timesyncd.service.in b/units/systemd-timesyncd.service.in
index 2d8d14f6de0f5c5670bebc7c90237db798184ccc..2136a85b351a757a7fd58aa5b0a391920aab2ebe 100644 (file)
--- a/units/systemd-timesyncd.service.in
+++ b/units/systemd-timesyncd.service.in
@@ -15,6 +15,7 @@ ConditionVirtualization=!container
 DefaultDependencies=no
 After=systemd-remount-fs.service systemd-sysusers.service
 Before=time-set.target sysinit.target shutdown.target
+Conflicts=chronyd.service ntpd.service
 Conflicts=shutdown.target
 Wants=time-set.target time-sync.target