On Sat, 24 Nov 2018 at 02:25, Stanislav Brabec <sbrabec@xxxxxxx> wrote:
> Karel Zak wrote:
> > On Wed, Nov 21, 2018 at 09:04:37PM +0100, Stanislav Brabec wrote:
> >> Add rfkill-block@.service and rfkill-unblock@.service templates.
> >> These make rfkill integration to systemd easier.
> >>
> >> Files come from openSUSE rfkill package.
> >>
> >> Example:
> >> Use `systemctl {start,stop} rfkill-block@bluetooth` to block or unblock
> >> (disable or enable) the bluetooth device.
> >
> > OK, but why? ;-)
> >
> > Does anything within systemd depend on rfkill? I guess for humans is
> > more friendly to call "rfkill unblock bluetooth" than use systemctl.
>
> I am not sure about use case of the original author, but I guess
> that it can be useful for suspend target and automatic unblocking when
> using on demand services (e. g. bluetooth service called after
> rfkill-unblock@bluetooth).
systemd has service[1] to maintain RF kill switch state as requested across
reboots. I think these rfkill-{block,unblock}@{target} files are
convenience services to change RF kill states with systemctl. That said,
getting a clarification from Jochen would nice because otherwise we are
simply guessing.
[1] https://www.freedesktop.org/software/systemd/man/systemd-rfkill.service.html
--
Sami Kerola
http://www.iki.fi/kerolasa/
