From 2dd79846ddd5f31aaf178eb3457677139e38fac0 Mon Sep 17 00:00:00 2001 From: "Peter A. Bigot" Date: Mon, 9 Apr 2018 13:39:16 -0500 Subject: time-wait-sync: use watchfile to coordinate with timesyncd Systems that have an accurate real-time clock may have an initial unsynchronized time that is close enough to the synchronized time that the final adjustment doesn't trigger a waking "clock set" event. Have timesyncd touch a file in its runtime directory as a secondary signal for synchronization. Continue to support the timerfd-based trigger as a sufficient condition when the watchfile is not present. Closes issue #8683 --- 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 d3bc4e9841..5b8b243f17 100644 --- a/units/systemd-timesyncd.service.in +++ b/units/systemd-timesyncd.service.in @@ -37,6 +37,7 @@ MemoryDenyWriteExecute=yes RestrictRealtime=yes RestrictNamespaces=yes RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6 +RuntimeDirectory=systemd/timesync SystemCallFilter=~@cpu-emulation @debug @keyring @module @mount @obsolete @raw-io @reboot @swap SystemCallArchitectures=native LockPersonality=yes -- cgit v1.2.3