blob: d40a14c698ac2d7888fe7126c0a01547ed31f71c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
|
<?xml version='1.0'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article>
<section>
<title>udevmonitor</title>
<refentry>
<refentryinfo>
<title>udevmonitor</title>
<date>August 2005</date>
<productname>udev</productname>
</refentryinfo>
<refmeta>
<refentrytitle>udevmonitor</refentrytitle>
<manvolnum>8</manvolnum>
<refmiscinfo class="version"></refmiscinfo>
</refmeta>
<refnamediv>
<refname>udevmonitor</refname>
<refpurpose>print the kernel and udev event sequence to the console</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
<command>udevmonitor</command>
<arg><option>--env</option></arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1><title>DESCRIPTION</title>
<para>udevmonitor listens to the kernel uevents and events send out by a udev rule
and prints the devpath of the event to the console. It can be used analyze to the
event timing by comparing the timestamps of the kernel uevent with the udev event.
</para>
</refsect1>
<refsect1><title>OPTIONS</title>
<variablelist>
<varlistentry>
<term><option>--env</option></term>
<listitem>
<para>Print the complete environment for all events. Can be used to compare the
kernel supplied and the udev added environment values.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1><title>AUTHOR</title>
<para>Written by Kay Sievers <email>kay.sievers@vrfy.org</email>.</para>
</refsect1>
<refsect1>
<title>SEE ALSO</title>
<para><citerefentry>
<refentrytitle>udev</refentrytitle><manvolnum>7</manvolnum>
</citerefentry></para>
</refsect1>
</refentry>
</section>
</article>
|
