[systemd-devel] [udev] Limitation of capturing remove events?

Is it a limitation or bug that I can only capture remove events with purely SUBSYSTEM or KENREL match, but not with ATTR{*} or even DRIVER? I unplugged and re-plugged the specific device once before each `cat test`: [tom@localhost ~]$ cat /etc/udev/rules.d/usb.rules KERNEL=="1-14",

Re: [systemd-devel] [udev] Limitation of capturing remove events?

On Tue, Sep 1, 2015 at 6:32 AM, Tom Yan wrote: > Is it a limitation or bug that I can only capture remove events with > purely SUBSYSTEM or KENREL match, but not with ATTR{*} or even DRIVER? > AFAIK, the former two come from the uevent itself, but the latter are always read

Re: [systemd-devel] [udev] Limitation of capturing remove events?

Also attach a log of `udevadm monitor` for your reference. On 1 September 2015 at 11:32, Tom Yan wrote: > Is it a limitation or bug that I can only capture remove events with > purely SUBSYSTEM or KENREL match, but not with ATTR{*} or even DRIVER? > > I unplugged and