summaryrefslogtreecommitdiff
path: root/debian
diff options
context:
space:
mode:
authorKevin Kuehler <[email protected]>2019-11-27 16:09:56 -0800
committerKevin Kuehler <[email protected]>2019-11-27 16:29:39 -0800
commitc9f07e855e2abac9c1a29cd412d888500a6a0bbb (patch)
tree2b7f3996b9596446a548d7b1db6357ffdcef6f21 /debian
parentbb84c9b65cd180e7de0f4718cd6030ada0b2bbba (diff)
systemd: fix zerotier hanging on shutdown
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
Diffstat (limited to 'debian')
-rw-r--r--debian/zerotier-one.service2
1 files changed, 1 insertions, 1 deletions
diff --git a/debian/zerotier-one.service b/debian/zerotier-one.service
index 133d4490..9d6a21b0 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]