[systemd-devel] [BUG] too many rfkill services

[Lennart Poettering]

On Thu, 20.11.14 06:40, Andrei Borzenkov (arvidjaar at gmail.com) wrote:

> В Tue, 18 Nov 2014 18:37:03 +0100
> Łukasz Stelmach <stlman at poczta.fm> пишет:
> 
> > 
> > After several suspend/resumes systemctl shows more than three dozens of
> > rfkill devices even though I've got only one BT and one WLAN.
> > 
> > --8<---------------cut here---------------start------------->8---
> > systemd-rfkill at rfkill0.service   loaded active exited    Load/Save RF Kill Switch Status of rfkill0
> > systemd-rfkill at rfkill1.service   loaded active exited    Load/Save RF Kill Switch Status of rfkill1
> > systemd-rfkill at rfkill2.service  loaded active exited    Load/Save RF Kill Switch Status of rfkill4
> > systemd-rfkill at rfkill3.service  loaded active exited    Load/Save RF Kill Switch Status of rfkill4
> > 
> 
> I confirm it.
> 
> [...]
> > 
> > The actual issue as I see it is that systemd does not stop and remove
> > rfkill services that refer to nonexistent devices.
> > 
> 
> The problem is, there no easy way to build device name from rfkillN for
> BindsTo. May be additional format specifier that would query udev
> database. Alternatively systemd-rfkill can be changed to accept sysfs
> path directly.

BindsTo= does not cause an exited-but-failed service to be flushed
out. It just stops running services when another service is ending,
that's all.

Lennart

-- 
Lennart Poettering, Red Hat