Ich habe einige Arch-Installationen in meiner administrativen Hoheit. Auf einigen, nicht auf allen, startet der systemd-resolved nicht mehr seit dem Upgrade:
systemd (257-1 -> 257.1-1)
Ich glaube, weil er jetzt zu früh startet:
Dec 22 18:02:36 systemd[1]: Starting Network Name Resolution...
Dec 22 18:02:36 (resolved)[850]: Failed to create destination mount point node '/run/systemd/mount-rootfs/var/tmp', ignoring: Operation not permitted
Dec 22 18:02:36 (resolved)[850]: Failed to mount /run/systemd/unit-private-tmp/var-tmp to /run/systemd/mount-rootfs/var/tmp: No such file or directory
Dec 22 18:02:36 (resolved)[850]: systemd-resolved.service: Failed to set up mount namespacing: /var/tmp: No such file or directory
Dec 22 18:02:36 (resolved)[850]: systemd-resolved.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-resolved: No such file or directory
Dec 22 18:02:36 systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=226/NAMESPACE
Dec 22 18:02:36 systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
Dec 22 18:02:36 systemd[1]: Failed to start Network Name Resolution.
…
Dec 22 18:02:37 systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 1.
Dec 22 18:02:37 systemd[1]: Starting Network Name Resolution...
Dec 22 18:02:37 systemd[1]: Started Network Name Resolution.
Ich habe mir pragmatisch so beholfen:
# /etc/systemd/system/systemd-resolved.service.d/override.conf
[Service]
RestartSec=1s
Damit geht es wieder (siehe oben).