From 0607a0add0b3ac72169be53d072db48c31a018d7 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Wed, 16 Aug 2017 23:07:40 -0400 Subject: Update for systemd 234 systemd commit c7fb922 (which appeared in 234) changed systemd-timesyncd from `ProtectSystem=full` to `ProtectSystem=strict`. This meant that it didn't have access to the /run/timesyncd/ sockets that we use. --- systemd-timesyncd.service.d-wait.conf.in | 1 + 1 file changed, 1 insertion(+) diff --git a/systemd-timesyncd.service.d-wait.conf.in b/systemd-timesyncd.service.d-wait.conf.in index 2b29b52..9ea5c42 100644 --- a/systemd-timesyncd.service.d-wait.conf.in +++ b/systemd-timesyncd.service.d-wait.conf.in @@ -8,4 +8,5 @@ ExecStart= ExecStart=@rootlibexecdir@/systemd-timesyncd-wrap @TIMESYNCD_PATH@ ExecStopPost=@RM@ -f -- /run/timesyncd/notify.sock ExecStartPre=@RM@ -f -- /run/timesyncd/notify.sock +ReadWritePaths=/run/timesyncd NotifyAccess=all -- cgit v1.1-4-g5e80