SYSTEMD-RFKILL.SERVICE(8)
๐ SYSTEMD-RFKILL.SERVICE ๐
okay bestie, so the manual name is SYSTEMD-RFKILL.SERVICE(8) and the whole family here is systemd-rfkill.service, systemd-rfkill.socket and systemd-rfkill โ and what do they do? they load and save the RF kill switch state at boot and on change. periodt. ๐
โจ NAME โจ
systemd-rfkill.service, systemd-rfkill.socket, systemd-rfkill โ literally the trio that loads and saves your RF kill switch state at boot and every time it changes ๐ฆ
๐ธ SYNOPSIS ๐ธ
systemd-rfkill.service
systemd-rfkill.socket
/usr/lib/systemd/systemd-rfkill
๐ DESCRIPTION ๐
so systemd-rfkill.service is that girl: she restores the RF kill switch state super early at boot, and then she saves it every single time it changes. no cap. ๐
and where does she keep all that? on disk, the RF kill switch state lives in /var/lib/systemd/rfkill/. iconic storage behaviour honestly. ๐๏ธโจ
๐ฅ KERNEL COMMAND LINE ๐ฅ
ok so systemd-rfkill understands the following kernel command line parameter. and if you wanna know more about that whole scene, go check kernel-command-line(7). iykyk ๐
systemd.restore_state=โ takes a boolean argument, and it defaults to"1". but if you set it to"0", it does not restore the rfkill settings on boot. HOWEVER โ and this is the plot twist โ the settings will still be stored on shutdown. she's not letting go, bestie ๐ญ๐
added in version 227, so it's been doing this for a minute ๐
๐ซถ SEE ALSO ๐ซถ
and that's the whole page, babe โจ this lil writeup came from systemd 262.1, dated like the classic it is โ mwah, stay slay, go restore some state ๐ ๐๐ธ
๐ฆ where this page comes from
- arch rolling: systemd 262.1-1 ยท LGPL-2.1-or-later AND CC0-1.0 AND GPL-2.0-or-later AND MIT-0
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms