From 971a7a1526a6c1d5cb439a8a41dc65ccd4e3a66f Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Mon, 22 Jul 2019 15:58:08 +0200 Subject: 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. --- units/systemd-timesyncd.service.in | 1 + 1 file changed, 1 insertion(+) (limited to 'units/systemd-timesyncd.service.in') diff --git a/units/systemd-timesyncd.service.in b/units/systemd-timesyncd.service.in index 2d8d14f6de..2136a85b35 100644 --- 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 -- cgit v1.2.3