picnoir/Systemd
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

"record_failed" -> "fail_event_on_error"

Browse source
This commit is contained in:
Kay Sievers 2009-08-06 19:23:06 +02:00
parent f7c5b04f69
commit 16dd0aa922
3 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
NEWS
View file

@ -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.

2
udev/udev-rules.c
View file

@ -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;

6
udev/udev.xml
View file

@ -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