units: order systemd-rfkill.socket after /var/lib/systemd/rfkill (#10904)

Otherwise we might install the socket unit early, but the service
backing it late, and then end up in strange loops when we enter rescue
mode, because we saw an event on /dev/rfkill but really can't dispatch
it nor flush it.

Fixes: #9171

diff --git a/units/systemd-rfkill.socket b/units/systemd-rfkill.socket
index c8e9f71..9d40890 100644 (file)
--- a/units/systemd-rfkill.socket
+++ b/units/systemd-rfkill.socket
@@ -12,7 +12,8 @@ Description=Load/Save RF Kill Switch Status /dev/rfkill Watch
 Documentation=man:systemd-rfkill.socket(8)
 DefaultDependencies=no
 BindsTo=sys-devices-virtual-misc-rfkill.device
-After=sys-devices-virtual-misc-rfkill.device
+After=sys-devices-virtual-misc-rfkill.device systemd-remount-fs.service
+RequiresMountsFor=/var/lib/systemd/rfkill
 Conflicts=shutdown.target
 Before=shutdown.target