diff options
| author | Kay Sievers <kay.sievers@vrfy.org> | 2009-08-06 16:16:26 +0200 |
|---|---|---|
| committer | Kay Sievers <kay.sievers@vrfy.org> | 2009-08-06 16:16:26 +0200 |
| commit | f7c5b04f69e004912327f082be8645b65bb1ff5d (patch) | |
| tree | 7b3de9f37426e4b6b3204dd888950b027e235849 /udev/udev-rules.c | |
| parent | 6e4025dfc8c2f6955d678b9f011c1d3b392a6e3e (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 'udev/udev-rules.c')
| -rw-r--r-- | udev/udev-rules.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/udev/udev-rules.c b/udev/udev-rules.c index a174d5db40..5f6ed06c9c 100644 --- a/udev/udev-rules.c +++ b/udev/udev-rules.c @@ -1379,7 +1379,7 @@ static int add_rule(struct udev_rules *rules, char *line, int flag = 0; attr = get_key_attribute(rules->udev, key + sizeof("RUN")-1); - if (attr != NULL && strstr(attr, "ignore_error")) + if (attr != NULL && strstr(attr, "record_failed")) flag = 1; rule_add_key(&rule_tmp, TK_A_RUN, op, value, &flag); continue; |