From c9f07e855e2abac9c1a29cd412d888500a6a0bbb Mon Sep 17 00:00:00 2001 From: Kevin Kuehler Date: Wed, 27 Nov 2019 16:09:56 -0800 Subject: [PATCH] systemd: fix zerotier hanging on shutdown MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On system shutdown, zerotier is stopped after the network and gets itself into a connection timeout loop. It hits the TimeoutStopUSec= and is forcibly killed by SIGKILL. Order zerotier after network.target so it can shutdown gracefully while the network is still up. From systemd.special(7): at shutdown, a unit that is ordered after network.target will be stopped before the network — to whatever level it might be set up then — is shut down. It is hence useful when writing service files that require network access on shutdown, which should order themselves after this target, but not pull it in --- debian/zerotier-one.service | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/zerotier-one.service b/debian/zerotier-one.service index 133d4490c..9d6a21b0a 100644 --- a/debian/zerotier-one.service +++ b/debian/zerotier-one.service @@ -1,6 +1,6 @@ [Unit] Description=ZeroTier One -After=network-online.target +After=network-online.target network.target Wants=network-online.target [Service]