summaryrefslogtreecommitdiff
path: root/.gitignore
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 /.gitignore
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 '.gitignore')
0 files changed, 0 insertions, 0 deletions