From 6279910be7b26239ce7eb442b227a879cb66e24e Mon Sep 17 00:00:00 2001 From: Clayton Craft Date: Thu, 13 Aug 2026 14:01:59 -0700 Subject: [PATCH] timesyncd: order after systemd-resolved Our first resolve happens way before sockets.target, and systemd-resolved-varlink.socket has no ordering of its own, so there's nothing making sure the socket is listening by then. Without this the connect fails and we quietly fall back to getaddrinfo(), which is exactly the case the varlink path is there for. Order after both the service and the socket since either one is enough on its own but neither covers every install situation. For example resolved binds the socket itself when nothing hands it one, and on systems where only the socket is enabled the service isn't started at boot at all. --- units/systemd-timesyncd.service.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/units/systemd-timesyncd.service.in b/units/systemd-timesyncd.service.in index bc64e24140..c180971047 100644 --- a/units/systemd-timesyncd.service.in +++ b/units/systemd-timesyncd.service.in @@ -13,7 +13,7 @@ Documentation=man:systemd-timesyncd.service(8) ConditionCapability=CAP_SYS_TIME ConditionVirtualization=!container DefaultDependencies=no -After=systemd-sysusers.service +After=systemd-sysusers.service systemd-resolved.service systemd-resolved-varlink.socket Before=time-set.target sysinit.target shutdown.target Conflicts=shutdown.target Wants=time-set.target