diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2019-07-22 15:58:08 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2019-07-22 15:58:08 +0200 |
| commit | 971a7a1526a6c1d5cb439a8a41dc65ccd4e3a66f (patch) | |
| tree | d8af76d4e3c77c2576800d87973be0c948719330 | |
| parent | e5ea741c62f9747417eefd1d197ef6c8eea87047 (diff) | |
| download | systemd-971a7a1526a6c1d5cb439a8a41dc65ccd4e3a66f.tar.gz | |
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.
| -rw-r--r-- | units/systemd-timesyncd.service.in | 1 |
1 files changed, 1 insertions, 0 deletions
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 |