shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-13 23:21:08 +03:00
Code
42718282f5
systemd/units/systemd-rfkill.service.in

22 lines
700 B
SYSTEMD
Raw Normal View History

rfkill: add new rfkill tool to save/restore rfkill state across reboots This works analogous to the existing backlight and random seed services
2013-10-14 06:31:49 +04:00
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
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 15:32:48 +03:00
Description=Load/Save RF Kill Switch Status
Documentation=man:systemd-rfkill.service(8)
rfkill: add new rfkill tool to save/restore rfkill state across reboots This works analogous to the existing backlight and random seed services
2013-10-14 06:31:49 +04:00
DefaultDependencies=no
RequiresMountsFor=/var/lib/systemd/rfkill
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 15:32:48 +03:00
BindsTo=sys-devices-virtual-misc-rfkill.device
rfkill: add new rfkill tool to save/restore rfkill state across reboots This works analogous to the existing backlight and random seed services
2013-10-14 06:31:49 +04:00
Conflicts=shutdown.target
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 15:32:48 +03:00
After=sys-devices-virtual-misc-rfkill.device systemd-remount-fs.service
Before=shutdown.target
rfkill: add new rfkill tool to save/restore rfkill state across reboots This works analogous to the existing backlight and random seed services
2013-10-14 06:31:49 +04:00
[Service]
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 15:32:48 +03:00
Type=notify
ExecStart=@rootlibexecdir@/systemd-rfkill
units: specify timeouts for more oneshot services Even trivial service occasionally get stuck, for example when there's a problem with the journal. There's nothing more annoying that looking at the cylon eye for a job with an infinite timeout. Use standard 90s for jobs that do some work, and 30s for those which should be almost instantenous.
2015-04-17 04:41:18 +03:00
TimeoutSec=30s
Copy Permalink