summaryrefslogtreecommitdiff
path: root/udev
diff options
context:
space:
mode:
Diffstat (limited to 'udev')
-rw-r--r--udev/udev-rules.c2
-rw-r--r--udev/udev.xml6
2 files changed, 4 insertions, 4 deletions
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