From 2907e13d3761c836002008e679cb5c0ff57264b8 Mon Sep 17 00:00:00 2001 From: Michael Vogt Date: Wed, 21 Oct 2026 17:04:06 +0200 Subject: [PATCH] contrib: don't order the client HTTP socket after network-online.target quarry-client-http.socket only listens on 127.0.0.1, so it never needs the network. But being a socket it is also Before=sockets.target, so its After=network-online.target puts the network on the boot path: on a machine without a network sockets.target and basic.target wait for systemd-networkd-wait-online to time out (120s), and everything after them waits too. Drop the network-online ordering from the socket. The service keeps its own, so the actual fetches still wait for the network. Signed-off-by: Michael Vogt --- contrib/systemd/quarry-client-http.socket.in | 2 -- 1 file changed, 2 deletions(-) diff --git a/contrib/systemd/quarry-client-http.socket.in b/contrib/systemd/quarry-client-http.socket.in index d477729..d42e631 100644 --- a/contrib/systemd/quarry-client-http.socket.in +++ b/contrib/systemd/quarry-client-http.socket.in @@ -3,8 +3,6 @@ [Unit] Description=Socket for Quarry Client sysupdate HTTP Provider -Wants=network-online.target -After=network-online.target [Socket] ListenStream=127.0.0.1:@client_http_port@