Join GitHub today
Some systemd fixes revolving dbus and socket activation of systemd services #88158
Motivation for this change
Resolved wasnt being activated by dbus; which caused DNS errors to occur shortly after or during
Also fixed socket activation for
Second try of #87263
Hmmm... yeah it definitely was a regression that I started noticing since 19.03 or 19.09. It doesn't always happen, so maybe I shouldn't be so sure this actually fixed it. It seems like a rebuild that touches network configuration options make it more likely.
This will make dbus socket activation for it work When `systemd-resolved` is restarted; this would lead to unavailability of DNS lookups. You're supposed to use DBUS socket activation to buffer resolved requests; such that restarts happen without downtime
With this systemd buffers netlink messages in early boot from the kernel itself; and passes them on to networkd for processing once it's started. Makes sure no routing messages are missed. Also makes an alias so that dbus can activate this unit. Upstream has this too.
Upstream has this alias too; so that dbus activation works. What I don't fully understand is why this would ever be useful given this unit is already started way in early boot; even before dbus is up. But lets just keep behaviour similar to upstream and then ask these questions to upstream.