Filtering drivers and module events

Filtering drivers and module events

[Marco d'Itri]

[-- Attachment #1: Type: text/plain, Size: 351 bytes --]

# do not call hotplug.d and dev.d for "drivers" and "module" events
SUBSYSTEM=="drivers",	OPTIONS="last_rule"
SUBSYSTEM=="module",	OPTIONS="last_rule"

# udev_run_hotplugd, udev_run_devd ...

Why are the last_rule rules not working? I see that the events are still
being logged by the logger script in hotplug.d/default/.

-- 
ciao,
Marco

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Filtering drivers and module events

[Kay Sievers]

On Sun, Jul 03, 2005 at 01:25:30PM +0200, Marco d'Itri wrote:
> # do not call hotplug.d and dev.d for "drivers" and "module" events
> SUBSYSTEM="drivers",	OPTIONS="last_rule"
> SUBSYSTEM="module",	OPTIONS="last_rule"
> 
> # udev_run_hotplugd, udev_run_devd ...
> 
> Why are the last_rule rules not working? I see that the events are still
> being logged by the logger script in hotplug.d/default/.

On "non-device events" udev reads only rules with RUN keys defined, so it
ignores the OPTIONS. I will correct this now.

In the meantime, you may use RUN:="" to clear the list and make the RUN
key unchangeable by later rules.

Thanks,
Kay


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel