summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2022-02-22 16:21:29 +0100
committerYu Watanabe <watanabe.yu+github@gmail.com>2022-02-23 06:52:39 +0900
commitb547838000ad640dfd86618202c67680119383a5 (patch)
tree8f4421c011329b6562921e22f9ae3dbb8dd39ce1
parent05d8ad0f855a9d32e3509cb68cd54c6bf0003073 (diff)
downloadsystemd-b547838000ad640dfd86618202c67680119383a5.tar.gz
units: drop After=systemd-networkd.service from systemd-resolved.service
This ordering existed since resolved was first created, but there should not be any need to order the two services against each other, as resolved should be able to pick up networkd DNS metadata either way (as it works with inotify in /run). Let's drop this hence, and not cargo-cult this to eternity Also see: https://github.com/systemd/systemd/pull/22389#issuecomment-1045978403
-rw-r--r--units/systemd-resolved.service.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/units/systemd-resolved.service.in b/units/systemd-resolved.service.in
index dfe82e1e4d..91e7c141e3 100644
--- a/units/systemd-resolved.service.in
+++ b/units/systemd-resolved.service.in
@@ -15,7 +15,7 @@ Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-network-
Documentation=https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
DefaultDependencies=no
-After=systemd-sysusers.service systemd-networkd.service
+After=systemd-sysusers.service
Before=network.target nss-lookup.target shutdown.target
Conflicts=shutdown.target
Wants=nss-lookup.target