summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorKay Sievers <kay.sievers@vrfy.org>2009-08-06 16:16:26 +0200
committerKay Sievers <kay.sievers@vrfy.org>2009-08-06 16:16:26 +0200
commitf7c5b04f69e004912327f082be8645b65bb1ff5d (patch)
tree7b3de9f37426e4b6b3204dd888950b027e235849 /NEWS
parent6e4025dfc8c2f6955d678b9f011c1d3b392a6e3e (diff)
re-enable failed event tracking
It did not work for the last couple of releases. If RUN{record_failed}+="..." is given, a non-zero execution will mark the event as failed. Recorded failed events can be re-triggered with: udevadm trigger --type=failed The failed tracking _might_ be useful for things which might not be ready to be executed at early bootup, but a bit later when the needed dependencies are available. In many cases though, it indicates that something is used in a way it should not.
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS10
1 files changed, 9 insertions, 1 deletions
diff --git a/NEWS b/NEWS
index b36ace5c05..0f41c18bbe 100644
--- a/NEWS
+++ b/NEWS
@@ -1,7 +1,15 @@
udev 146
========
-New keymaps, new modem, hid2hci updated.
+Bugfixes.
+
+The udevadm trigger "--retry-failed" option, which is replaced since quite
+a while by "--type=failed" is removed.
+The failed tracking was not working at all for a few releases. The RUN
+option "ignore_error" is replaces by a "record_failed" option, and the
+default is not to track any failing RUN executions.
+
+New keymaps, new modem, hid2hci updated.
udev 145
========