"record_failed" -> "fail_event_on_error"

[elogind.git] / udev / udev.xml

diff --git a/udev/udev.xml b/udev/udev.xml
index cd4884d3b5529d4d98777536d0db3b97ece07e65..56fda1070d467deeb8e4d334961fc4adbf949d22 100644 (file)
--- a/udev/udev.xml
+++ b/udev/udev.xml
@@ -323,7 +323,8 @@
             <varlistentry>
               <term><option>ENV{<replaceable>key</replaceable>}</option></term>
               <listitem>
-                <para>Set a device property value.</para>
+                <para>Set a device property value. Property names with a leading '.'
+                are not stored in the database or exported to external tool or events.</para>
               </listitem>
             </varlistentry>
 
@@ -334,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>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