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.xml | |
| 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.xml')
| -rw-r--r-- | udev/udev.xml | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/udev/udev.xml b/udev/udev.xml index 934fe628ae..5aa6c38da4 100644 --- a/udev/udev.xml +++ b/udev/udev.xml @@ -335,7 +335,10 @@ device. This can only be used for very short running tasks. Running an 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.</para> + 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> <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 |