remove debug output during rules parsing

[elogind.git] / udev / udev.xml

diff --git a/udev/udev.xml b/udev/udev.xml
index dce953dbce10741ce2f02f3ce19624a28a38de7c..d2277c93d0d60e3b4b84ba3138237968ff9f5826 100644 (file)
--- a/udev/udev.xml
+++ b/udev/udev.xml
@@ -237,6 +237,13 @@
               </listitem>
             </varlistentry>
 
               </listitem>
             </varlistentry>
 

+            <varlistentry>
+              <term><option>TAG</option></term>
+              <listitem>
+                <para>Match against a device tag.</para>
+              </listitem>
+            </varlistentry>
+

             <varlistentry>
               <term><option>TEST{<replaceable>octal mode mask</replaceable>}</option></term>
               <listitem>
             <varlistentry>
               <term><option>TEST{<replaceable>octal mode mask</replaceable>}</option></term>
               <listitem>


@@ -297,8 +304,13 @@
             <varlistentry>
               <term><option>NAME</option></term>
               <listitem>
             <varlistentry>
               <term><option>NAME</option></term>
               <listitem>

-                <para>The name of the node to be created, or the name the network interface
-                should be renamed to.</para>
+                <para>The name, a network interface should be renamed to, or the name
+                a device node should be named. Usually the kernel provides the defined
+                node name, or even creates and removes the node before udev receives
+                any event. Changing the node name from the kernel's default may result
+                in unexpected behavior and is not supported. Udev is only expected to
+                handle device node permissions and to create additional symlinks, which
+                do not conflict with the kernel device node names.</para>

               </listitem>
             </varlistentry>
 
               </listitem>
             </varlistentry>
 


@@ -306,9 +318,16 @@
               <term><option>SYMLINK</option></term>
               <listitem>
                 <para>The name of a symlink targeting the node. Every matching rule will add
               <term><option>SYMLINK</option></term>
               <listitem>
                 <para>The name of a symlink targeting the node. Every matching rule will add

-                this value to the list of symlinks to be created along with the device  node.
+                this value to the list of symlinks to be created along with the device node.

                 Multiple symlinks may be specified by separating the names by the space
                 Multiple symlinks may be specified by separating the names by the space

-                character.</para>
+                character. In case multiple devices claim the same name, the link will
+                always point to the device with the highest link_priority. If the current device
+                goes away, the links will be re-evaluated and the device with the next highest
+                link_priority will own the link. If no link_priority is specified, the order
+                of the devices, and which of them will own the link, is undefined. Claiming
+                the same name for a node and links may result in unexpected behavior and is
+                not supported.
+                </para>

               </listitem>
             </varlistentry>
 
               </listitem>
             </varlistentry>
 


@@ -336,6 +355,19 @@
               </listitem>
             </varlistentry>
 
               </listitem>
             </varlistentry>
 

+            <varlistentry>
+              <term><option>TAG</option></term>
+              <listitem>
+                <para>Attach a tag to a device. This is used to filter events for users
+                of libudev's monitor functionality, or to enumerate a group of tagged
+                devices. The implementation can only work efficiently if only a few
+                tags are attached to a device. It is only meant to be used in
+                contexts with specific device filter requirements, and not as a
+                general-purpose flag. Excessive use might result in inefficient event
+                handling.</para>
+              </listitem>
+            </varlistentry>
+

             <varlistentry>
               <term><option>RUN</option></term>
               <listitem>
             <varlistentry>
               <term><option>RUN</option></term>
               <listitem>


@@ -426,7 +458,8 @@
             <varlistentry>
               <term><option>WAIT_FOR</option></term>
               <listitem>
             <varlistentry>
               <term><option>WAIT_FOR</option></term>
               <listitem>

-                <para>Wait for a file to become available.</para>
+                <para>Wait for a file to become available or until a 10
+                seconds timeout expires.</para>

               </listitem>
             </varlistentry>
 
               </listitem>
             </varlistentry>
 


@@ -461,7 +494,7 @@
                     <term><option>watch</option></term>
                     <listitem>
                       <para>Watch the device node with inotify, when closed after being opened for
                     <term><option>watch</option></term>
                     <listitem>
                       <para>Watch the device node with inotify, when closed after being opened for

-                     writing, a change uevent will be synthesised.</para>
+                      writing, a change uevent will be synthesised.</para>

                     </listitem>
                   </varlistentry>
                 </variablelist>
                     </listitem>
                   </varlistentry>
                 </variablelist>