devices claim the same name, the link always points to the device with
the highest link_priority. If the current device goes away, the links are
re-evaluated and the device with the next highest link_priority becomes the owner of
- the link. If no link_priority is specified, the order of the devices, and
- which one of them owns the link, is undefined. Claiming the same name for
- a symlink, which is or might be used for a device node, may result in
- unexpected behavior and is not supported.
+ the link. If no link_priority is specified, the order of the devices (and
+ which one of them owns the link) is undefined. Also, symlink names must
+ never conflict with the kernel's default device node names, as that would
+ result in unpredictable behavior.
</para>
</listitem>
</varlistentry>
<term><option>ENV{<replaceable>key</replaceable>}</option></term>
<listitem>
<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>
+ are neither stored in the database nor exported to events or
+ external tools (run by, say, the PROGRAM match key).</para>
</listitem>
</varlistentry>
this or a dependent device. Long running tasks need to be immediately
detached from the event process itself.</para>
<para>If no absolute path is given, the program is expected to live in
- <filename>/lib/udev</filename>, otherwise the absolute path must be
- specified. Program name and arguments are separated by spaces. Single quotes
- can be used to specify arguments with spaces.</para>
+ the directory provided at compile-time to configure via --libexecdir
+ (this is usually <filename>/lib/udev</filename>), otherwise the absolute
+ path must be specified. The program name and following arguments are
+ separated by spaces. Single quotes can be used to specify arguments with
+ spaces.</para>
</listitem>
</varlistentry>