units: move resolved to sysinit.target (from basic.target)
authorLennart Poettering <lennart@poettering.net>
Thu, 3 Feb 2022 11:15:00 +0000 (12:15 +0100)
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Thu, 24 Feb 2022 09:36:47 +0000 (10:36 +0100)
commit29a8fbf49a0d16a25db8968f67a1f76f3d2021e9
tree0c581712203b93d3e450205aef9b432f46e3b73b
parent0802f62efc1d1c67d5be67223b529c93536cf2ed
units: move resolved to sysinit.target (from basic.target)

79a67f3ca4d32c37b5e754501852a85eae908a6a pulled systemd-resolved.service
in from basic.target instead of multi-user.target, i.e. the idea is to
make it an early boot service, instead of a regular service.

However, early boot services are supposed to be in sysinit.target, not
basic.target (the latter is just one that combines the early boot
services in sysinit.target, the sockets in sockets.targt, the mounts in
local-fs.target and so on into one big target).

Also, the comit actually didn't add a synchronization point, i.e. not
Before=, so that the whole thing was racy.

Let's fix all that.

Follow-up for 79a67f3ca4d32c37b5e754501852a85eae908a6a
units/systemd-resolved.service.in