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