3 Commits

Author	SHA1	Message	Date
Lennart Poettering	7af002f71d	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	2018-11-24 23:59:37 +09:00
Zbigniew Jędrzejewski-Szmek	a7df2d1e43	Add SPDX license headers to unit files	2017-11-19 19:08:15 +01:00
Lennart Poettering	d35c1bb1f4	rfkill: rework and make it listen on /dev/rfkill ... With this rework we introduce systemd-rfkill.service as singleton that is activated via systemd-rfkill.socket that listens on /dev/rfkill. That way, we get notified each time a new rfkill device shows up or changes state, in which case we restore and save its current setting to disk. This is nicer than the previous logic, as this means we save/restore state even of rfkill devices that are around only intermittently, and save/restore the state even if the system is shutdown abruptly instead of cleanly. This implements what I suggested in #1019 and obsoletes it.	2015-10-01 16:21:09 +02:00