diff options
| author | Kay Sievers <kay.sievers@vrfy.org> | 2009-08-06 19:23:06 +0200 |
|---|---|---|
| committer | Kay Sievers <kay.sievers@vrfy.org> | 2009-08-06 19:23:06 +0200 |
| commit | 16dd0aa9223b5e3fc281765ac809754716266456 (patch) | |
| tree | c32c801b151c455d69513f0521542bb13a8becba | |
| parent | f7c5b04f69e004912327f082be8645b65bb1ff5d (diff) | |
"record_failed" -> "fail_event_on_error"
| -rw-r--r-- | NEWS | 2 | ||||
| -rw-r--r-- | udev/udev-rules.c | 2 | ||||
| -rw-r--r-- | udev/udev.xml | 6 |
3 files changed, 5 insertions, 5 deletions
@@ -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 5f6ed06c9c..03234fe2a1 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 5aa6c38da4..56fda1070d 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 - <option>RUN{<replaceable>record_failed</replaceable>}</option> is specified, - and the executed program returns non-zero, the event will be marked as failed - for a possible later handling.</para> + <option>RUN{<replaceable>fail_event_on_error</replaceable>}</option> is + specified, and the executed program returns non-zero, the event will be + marked as failed for a possible later handling.</para> <para>If the specified string starts with <option>socket:<replaceable>path</replaceable></option>, all current event values will be passed to the specified socket, as a message in the same |