Bug#809321: systemd-rfkill state save/restore issues

Yuri D'Elia wavexx at thregr.org
Tue Dec 29 10:49:32 GMT 2015


Package: systemd
Version: 228-2+b1
Severity: normal

[... after a few months wondering why wifi/rfkill doesn't work anymore as it
should, I bump into a newfound systemd-rfkill.service/socket]

I'd like my system to start soft-killed by default. I can do that with
laptop-mode-tools or tlp, but now both conflict in behavior with this service.

Fine for me, but apparently there's no way to make systemd-rfkill do what I
want.

My first question would be, why exactly do I need a *kernel* parameter
(systemd.restore_state) to change the restore behavior?

Looks like we require the state directory to be mounted, so there's no reason
this cannot be specified there. I get this might be useful for boot issues, but
only in *addition* to a configuration file.

Second, restore_state=0 doesn't prevent (as stated) to save at shutdown. If I
could prevent state changes to be saved, I would be fine to restore from my
(manually set) state.



More information about the Pkg-systemd-maintainers mailing list