summaryrefslogtreecommitdiff
path: root/rules/rules.d/95-udev-late.rules
diff options
context:
space:
mode:
authorKay Sievers <kay.sievers@vrfy.org>2009-03-29 04:24:39 +0200
committerKay Sievers <kay.sievers@vrfy.org>2009-03-29 04:24:39 +0200
commit116254097ad3c07d9f7ed06042dbec7ba4f0f4fd (patch)
treee2d79a92d01937d3d292badc93ffdb4130d51d7c /rules/rules.d/95-udev-late.rules
parent241e5a21f9ad7bc986e1bb74093adf9fdb98b170 (diff)
send monitor events back to netlink socket
Instead of of our own private monitor socket, we send the processed event back to our netlink socket, to the multicast group 2 -- so any number of users can listen to udev events, just like they can listen to kernel emitted events on group 1.
Diffstat (limited to 'rules/rules.d/95-udev-late.rules')
-rw-r--r--rules/rules.d/95-udev-late.rules4
1 files changed, 0 insertions, 4 deletions
diff --git a/rules/rules.d/95-udev-late.rules b/rules/rules.d/95-udev-late.rules
index 7207081d46..eca0faa5c5 100644
--- a/rules/rules.d/95-udev-late.rules
+++ b/rules/rules.d/95-udev-late.rules
@@ -2,7 +2,3 @@
# run a command on remove events
ACTION=="remove", ENV{REMOVE_CMD}!="", RUN+="$env{REMOVE_CMD}"
-
-# event to be catched by udevmonitor
-RUN+="socket:@/org/kernel/udev/monitor"
-