<para>Usually udev runs as <citerefentry><refentrytitle>udevd</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> and receives uevents directly from the
<para>Usually udev runs as <citerefentry><refentrytitle>udevd</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> and receives uevents directly from the
<para>If udev receives a device event, it matches its configured rules
against the available device attributes provided in sysfs to identify the device.
<para>If udev receives a device event, it matches its configured rules
against the available device attributes provided in sysfs to identify the device.
node name and multiple symlink names and instruct udev to run additional programs
as part of the device event handling.</para>
</refsect1>
node name and multiple symlink names and instruct udev to run additional programs
as part of the device event handling.</para>
</refsect1>
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>
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>
<term><option>PROGRAM</option></term>
<listitem>
<para>Execute external program. The key is true, if the program returns
<term><option>PROGRAM</option></term>
<listitem>
<para>Execute external program. The key is true, if the program returns
- without exit code zero. The whole event environment is available to the
- executed program. The program's output printed to stdout is available for
+ with exit code zero. The whole event environment is available to the
+ executed program. The program's output printed to stdout, is available in