pointing to the node, or run a specified program as part of the event handling.
If no matching rule is found, the default device node name is used.</para>
- <para>A rule may consist of a list of one or more key value pairs separated by
+ <para>A rule consists of a list of one or more key value pairs separated by
a comma. Each key has a distinct operation, depending on the used operator. Valid
operators are:</para>
<variablelist>
<varlistentry>
<term><option>!=</option></term>
<listitem>
- <para>Compare for non-equality.</para>
+ <para>Compare for inequality.</para>
</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. Only one rule can set the node name, all later rules with
- a NAME key will be ignored.</para>
+ should be renamed to.</para>
</listitem>
</varlistentry>
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>
- <para>If the specifiefd string starts with
+ <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
format the kernel sends an uevent. If the first character of the specified path
with this option.</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <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>
+ </listitem>
+ </varlistentry>
</variablelist>
</listitem>
</varlistentry>