re-enable failed event tracking

[elogind.git] / udev / udev.xml

diff --git a/udev/udev.xml b/udev/udev.xml
index 934fe628ae66dbdf226a1d0f97d46ff8b0ecb1e8..5aa6c38da4f844d2839661349b76a6e3a305dd8c 100644 (file)
--- 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