From: Kay Sievers Date: Thu, 6 Aug 2009 17:23:06 +0000 (+0200) Subject: "record_failed" -> "fail_event_on_error" X-Git-Tag: 174~861 X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=commitdiff_plain;h=16dd0aa9223b5e3fc281765ac809754716266456;p=elogind.git "record_failed" -> "fail_event_on_error" --- diff --git a/NEWS b/NEWS index 0f41c18bb..914b9498f 100644 --- a/NEWS +++ b/NEWS @@ -6,7 +6,7 @@ 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 +option "ignore_error" is replaced by a "fail_event_on_error" option, and the default is not to track any failing RUN executions. New keymaps, new modem, hid2hci updated. diff --git a/udev/udev-rules.c b/udev/udev-rules.c index 5f6ed06c9..03234fe2a 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, "record_failed")) + if (attr != NULL && strstr(attr, "fail_event_on_error")) flag = 1; rule_add_key(&rule_tmp, TK_A_RUN, op, value, &flag); continue; diff --git a/udev/udev.xml b/udev/udev.xml index 5aa6c38da..56fda1070 100644 --- a/udev/udev.xml +++ b/udev/udev.xml @@ -336,9 +336,9 @@ event process for a long period of time may block all further events for this or a dependent device. Long running tasks need to be immediately detached from the event process itself. If the option - is specified, - and the executed program returns non-zero, the event will be marked as failed - for a possible later handling. + is + specified, and the executed program returns non-zero, the event will be + marked as failed for a possible later handling. If the specified string starts with , all current event values will be passed to the specified socket, as a message in the same