diff options
| author | Lennart Poettering <lennart@poettering.net> | 2013-10-14 18:52:07 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2013-10-14 19:02:44 +0200 |
| commit | f6f738db7273f8a2092ac372852f37f2a34cea17 (patch) | |
| tree | dfc5717d462076cd9baf4f73494e9cb593afea0b /rules/99-systemd.rules.in | |
| parent | a8ccacf5344c4434b1d5ff3837307acb8fcf93d2 (diff) | |
rfkill: use ID_PATH as identifier for rfkill state files
Let's include the stable device path for the rfkill devices in the name
of the file we store the rfkill state in, so that we have some stability
regarding enumeration order.
Diffstat (limited to 'rules/99-systemd.rules.in')
| -rw-r--r-- | rules/99-systemd.rules.in | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/rules/99-systemd.rules.in b/rules/99-systemd.rules.in index 2ffe74441..8e877809a 100644 --- a/rules/99-systemd.rules.in +++ b/rules/99-systemd.rules.in @@ -59,7 +59,7 @@ ACTION=="add", SUBSYSTEM=="leds", KERNEL=="*kbd_backlight", TAG+="systemd", ENV{ # Pull in rfkill save/restore for all rfkill devices -ACTION=="add", SUBSYSTEM=="rfkill", TAG+="systemd", ENV{SYSTEMD_WANTS}+="systemd-rfkill@rfkill:$name.service" +ACTION=="add", SUBSYSTEM=="rfkill", TAG+="systemd", IMPORT{builtin}="path_id", ENV{SYSTEMD_WANTS}+="systemd-rfkill@$name.service" # Asynchronously mount file systems implemented by these modules as # soon as they are loaded. |