shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-26 03:22:00 +03:00
Code

man pages: work around xmlto which tries to be smart

Browse Source
This commit is contained in:
Kay Sievers 2006-07-29 02:08:58 +02:00
parent 21dabee8a7
commit 660508cdcb
16 changed files with 136 additions and 205 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

108
udev.7
View File

@ -1,7 +1,10 @@
.\" ** You probably do not want to edit this file directly ** .\" Title: udev
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1). .\" Author:
.\" Instead of manually editing it, you probably should edit the DocBook XML .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it. .\" Date: August 2005
.\" Manual: udev
.\" Source: udev
.\"
.TH "UDEV" "7" "August 2005" "udev" "udev" .TH "UDEV" "7" "August 2005" "udev" "udev"
.\" disable hyphenation .\" disable hyphenation
.nh .nh
@ -28,22 +31,23 @@ All udev configuration files are placed in
.PP .PP
udev expects its main configuration file at udev expects its main configuration file at
\fI/etc/udev/udev.conf\fR. It consists of a set of variables allowing the user to override default udev values. The following variables can be set: \fI/etc/udev/udev.conf\fR. It consists of a set of variables allowing the user to override default udev values. The following variables can be set:
.TP .TP 3n
\fBudev_root\fR \fBudev_root\fR
Specifies where to place the device nodes in the filesystem. The default value is Specifies where to place the device nodes in the filesystem. The default value is
\fI/dev\fR. \fI/dev\fR.
.TP .TP 3n
\fBudev_rules\fR \fBudev_rules\fR
The name of the udev rules file or directory to look for files with the suffix The name of the udev rules file or directory to look for files with the suffix
\fI.rules\fR. Multiple rule files are read in lexical order. The default value is \fI.rules\fR. Multiple rule files are read in lexical order. The default value is
\fI/etc/udev/rules.d\fR. \fI/etc/udev/rules.d\fR.
.TP .TP 3n
\fBudev_log\fR \fBudev_log\fR
The logging priority. Valid values are the numerical syslog priorities or their textual representations: The logging priority. Valid values are the numerical syslog priorities or their textual representations:
\fBerr\fR, \fBerr\fR,
\fBinfo\fR \fBinfo\fR
and and
\fBdebug\fR. \fBdebug\fR.
.\" end of SS subsection "Configuration file"
.SS "Rules files" .SS "Rules files"
.PP .PP
The udev rules are read from the files located in the The udev rules are read from the files located in the
@ -51,105 +55,105 @@ The udev rules are read from the files located in the
directory or at the location specified value in the configuraton file. Every line in the rules file contains at least one key value pair. There are two kind of keys, match and assignement keys. If all match keys are matching against its value, the rule gets applied and the assign keys get the specified value assigned. A matching rule may specify the name of the device node, add a symlink 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. directory or at the location specified value in the configuraton file. Every line in the rules file contains at least one key value pair. There are two kind of keys, match and assignement keys. If all match keys are matching against its value, the rule gets applied and the assign keys get the specified value assigned. A matching rule may specify the name of the device node, add a symlink 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.
.PP .PP
A rule may 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: A rule may 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:
.TP .TP 3n
\fB==\fR \fB==\fR
Compare for equality. Compare for equality.
.TP .TP 3n
\fB!=\fR \fB!=\fR
Compare for non\-equality. Compare for non\-equality.
.TP .TP 3n
\fB=\fR \fB=\fR
Asign a value to a key. Keys that represent a list, are reset and only this single value is assigned. Asign a value to a key. Keys that represent a list, are reset and only this single value is assigned.
.TP .TP 3n
\fB+=\fR \fB+=\fR
Add the value to a key that holds a list of entries. Add the value to a key that holds a list of entries.
.TP .TP 3n
\fB:=\fR \fB:=\fR
Assign a value to a key finally; disallow any later changes, which may be used to prevent changes by any later rules. Assign a value to a key finally; disallow any later changes, which may be used to prevent changes by any later rules.
.PP .PP
The following key names can be used to match against device properties: The following key names can be used to match against device properties:
.TP .TP 3n
\fBACTION\fR \fBACTION\fR
Match the name of the event action. Match the name of the event action.
.TP .TP 3n
\fBKERNEL\fR \fBKERNEL\fR
Match the name of the device. Match the name of the device.
.TP .TP 3n
\fBDEVPATH\fR \fBDEVPATH\fR
Match the devpath of the device. Match the devpath of the device.
.TP .TP 3n
\fBSUBSYSTEM\fR \fBSUBSYSTEM\fR
Match the subsystem of the device. Match the subsystem of the device.
.TP .TP 3n
\fBBUS\fR \fBBUS\fR
Search the devpath upwards for a matching device subsystem name. Search the devpath upwards for a matching device subsystem name.
.TP .TP 3n
\fBDRIVER\fR \fBDRIVER\fR
Search the devpath upwards for a matching device driver name. Search the devpath upwards for a matching device driver name.
.TP .TP 3n
\fBID\fR \fBID\fR
Search the devpath upwards for a matching device name. Search the devpath upwards for a matching device name.
.TP .TP 3n
\fBSYSFS{\fR\fB\fIfilename\fR\fR\fB}\fR \fBSYSFS{\fR\fB\fIfilename\fR\fR\fB}\fR
Search the devpath upwards for a device with matching sysfs attribute values. Up to five Search the devpath upwards for a device with matching sysfs attribute values. Up to five
\fBSYSFS\fR \fBSYSFS\fR
keys can be specified per rule. All attributes must match on the same device. Trailing whitespace in the attribute values is ignored, if the specified match value does not contain trailing whitespace itself. keys can be specified per rule. All attributes must match on the same device. Trailing whitespace in the attribute values is ignored, if the specified match value does not contain trailing whitespace itself.
.TP .TP 3n
\fBENV{\fR\fB\fIkey\fR\fR\fB}\fR \fBENV{\fR\fB\fIkey\fR\fR\fB}\fR
Match against the value of an environment variable. Up to five Match against the value of an environment variable. Up to five
\fBENV\fR \fBENV\fR
keys can be specified per rule. This key can also be used to export a variable to the environment. keys can be specified per rule. This key can also be used to export a variable to the environment.
.TP .TP 3n
\fBPROGRAM\fR \fBPROGRAM\fR
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 the RESULT key. 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 the RESULT key.
.TP .TP 3n
\fBRESULT\fR \fBRESULT\fR
Match the returned string of the last PROGRAM call. This key can be used in the same or in any later rule after a PROGRAM call. Match the returned string of the last PROGRAM call. This key can be used in the same or in any later rule after a PROGRAM call.
.PP .PP
Most of the fields support a shell style pattern matching. The following pattern characters are supported: Most of the fields support a shell style pattern matching. The following pattern characters are supported:
.TP .TP 3n
\fB*\fR \fB*\fR
Matches zero, or any number of characters. Matches zero, or any number of characters.
.TP .TP 3n
\fB?\fR \fB?\fR
Matches any single character. Matches any single character.
.TP .TP 3n
\fB[]\fR \fB[]\fR
Matches any single character specified within the brackets. example, the pattern string 'tty[SR]' would match either 'ttyS' or 'ttyR'. Ranges are also supported within this match with the '\-' character. For example, to match on the range of all digits, the pattern [0\-9] would be used. If the first character following the '[' is a '!', any characters not enclosed are matched. Matches any single character specified within the brackets. example, the pattern string 'tty[SR]' would match either 'ttyS' or 'ttyR'. Ranges are also supported within this match with the '\-' character. For example, to match on the range of all digits, the pattern [0\-9] would be used. If the first character following the '[' is a '!', any characters not enclosed are matched.
.PP .PP
The following keys can get values assigned: The following keys can get values assigned:
.TP .TP 3n
\fBNAME\fR \fBNAME\fR
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. 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.
.TP .TP 3n
\fBSYMLINK\fR \fBSYMLINK\fR
The name of a symlink targeting the node. Every matching rule can add 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 character. The name of a symlink targeting the node. Every matching rule can add 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 character.
.TP .TP 3n
\fBOWNER, GROUP, MODE\fR \fBOWNER, GROUP, MODE\fR
The permissions for the device node. Every specified value overwrites the compiled\-in default value. The permissions for the device node. Every specified value overwrites the compiled\-in default value.
.TP .TP 3n
\fBENV{\fR\fB\fIkey\fR\fR\fB}\fR \fBENV{\fR\fB\fIkey\fR\fR\fB}\fR
Export a variable to the environment. This key can also be used to match against an environment variable. Export a variable to the environment. This key can also be used to match against an environment variable.
.TP .TP 3n
\fBRUN\fR \fBRUN\fR
Add a program to the list of programs to be executed for a specific device. This can only be used for very short running tasks. Running an 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. Add a program to the list of programs to be executed for a specific device. This can only be used for very short running tasks. Running an 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.
.TP .TP 3n
\fBLABEL\fR \fBLABEL\fR
Named label where a GOTO can jump to. Named label where a GOTO can jump to.
.TP .TP 3n
\fBGOTO\fR \fBGOTO\fR
Jumps to the next LABEL with a matching name Jumps to the next LABEL with a matching name
.TP .TP 3n
\fBIMPORT{\fR\fB\fItype\fR\fR\fB}\fR \fBIMPORT{\fR\fB\fItype\fR\fR\fB}\fR
Import the printed result or the value of a file in environment key format into the event environment. Import the printed result or the value of a file in environment key format into the event environment.
\fBprogram\fR \fBprogram\fR
will execute an external program and read its output. will execute an external program and read its output.
\fBfile\fR \fBfile\fR
will inport a text file. If no option is given, udev will determine it from the executable bit of of the file permissions. will inport a text file. If no option is given, udev will determine it from the executable bit of of the file permissions.
.TP .TP 3n
\fBWAIT_FOR_SYSFS\fR \fBWAIT_FOR_SYSFS\fR
Wait for the specified sysfs file of the device to be created. Can be used to fight against kernel sysfs timing issues. Wait for the specified sysfs file of the device to be created. Can be used to fight against kernel sysfs timing issues.
.TP .TP 3n
\fBOPTIONS\fR \fBOPTIONS\fR
\fBlast_rule\fR \fBlast_rule\fR
stops further rules application. No later rules will have any effect. stops further rules application. No later rules will have any effect.
@ -171,56 +175,58 @@ and
fields support simple printf\-like string substitutions. The fields support simple printf\-like string substitutions. The
\fBRUN\fR \fBRUN\fR
format chars gets applied after all rules have been processed, right before the program is executed. It allows the use of the complete environment set by earlier matching rules. For all other fields, substitutions are applied while the individual rule is being processed. The available substitutions are: format chars gets applied after all rules have been processed, right before the program is executed. It allows the use of the complete environment set by earlier matching rules. For all other fields, substitutions are applied while the individual rule is being processed. The available substitutions are:
.TP .TP 3n
\fB$kernel\fR, \fB%k\fR \fB$kernel\fR, \fB%k\fR
The kernel name for this device. The kernel name for this device.
.TP .TP 3n
\fB$number\fR, \fB%n\fR \fB$number\fR, \fB%n\fR
The kernel number for this device. For example, 'sda3' has kernel number of '3' The kernel number for this device. For example, 'sda3' has kernel number of '3'
.TP .TP 3n
\fB$devpath\fR, \fB%p\fR \fB$devpath\fR, \fB%p\fR
The devpath of the device. The devpath of the device.
.TP .TP 3n
\fB$id\fR, \fB%b\fR \fB$id\fR, \fB%b\fR
The name of the device matched while searching the devpath upwards for The name of the device matched while searching the devpath upwards for
\fBBUS\fR, \fBBUS\fR,
\fBID\fR\fBDRIVER\fR \fBID\fR
\fBDRIVER\fR
and and
\fBSYSFS\fR. \fBSYSFS\fR.
.TP .TP 3n
\fB$sysfs{\fR\fB\fIfile\fR\fR\fB}\fR, \fB%s{\fR\fB\fIfile\fR\fR\fB}\fR \fB$sysfs{\fR\fB\fIfile\fR\fR\fB}\fR, \fB%s{\fR\fB\fIfile\fR\fR\fB}\fR
The value of a sysfs attribute found at the current or a parent device. The value of a sysfs attribute found at the current or a parent device.
.TP .TP 3n
\fB$env{\fR\fB\fIkey\fR\fR\fB}\fR, \fB%E{\fR\fB\fIkey\fR\fR\fB}\fR \fB$env{\fR\fB\fIkey\fR\fR\fB}\fR, \fB%E{\fR\fB\fIkey\fR\fR\fB}\fR
The value of an environment variable. The value of an environment variable.
.TP .TP 3n
\fB$major\fR, \fB%M\fR \fB$major\fR, \fB%M\fR
The kernel major number for the device. The kernel major number for the device.
.TP .TP 3n
\fB$minor\fR \fB%m\fR \fB$minor\fR \fB%m\fR
The kernel minor number for the device. The kernel minor number for the device.
.TP .TP 3n
\fB$result\fR, \fB%c\fR \fB$result\fR, \fB%c\fR
The string returned by the external program requested with PROGRAM. A single part of the string, separated by a space character may be selected by specifying the part number as an attribute: The string returned by the external program requested with PROGRAM. A single part of the string, separated by a space character may be selected by specifying the part number as an attribute:
\fB%c{N}\fR. If the number is followed by the '+' char this part plus all remaining parts of the result string are substituted: \fB%c{N}\fR. If the number is followed by the '+' char this part plus all remaining parts of the result string are substituted:
\fB%c{N+}\fR \fB%c{N+}\fR
.TP .TP 3n
\fB$parent\fR, \fB%P\fR \fB$parent\fR, \fB%P\fR
The node name of the parent device. The node name of the parent device.
.TP .TP 3n
\fB$root\fR, \fB%r\fR \fB$root\fR, \fB%r\fR
The udev_root value. The udev_root value.
.TP .TP 3n
\fB$tempnode\fR, \fB%N\fR \fB$tempnode\fR, \fB%N\fR
The name of a created temporary device node to provide access to the device from a external program before the real node is created. The name of a created temporary device node to provide access to the device from a external program before the real node is created.
.TP .TP 3n
\fB%%\fR \fB%%\fR
The '%' character itself. The '%' character itself.
.TP .TP 3n
\fB$$\fR \fB$$\fR
The '$' character itself. The '$' character itself.
.PP .PP
The count of characters to be substituted may be limited by specifying the format length value. For example, '%3s{file}' will only insert the first three characters of the sysfs attribute The count of characters to be substituted may be limited by specifying the format length value. For example, '%3s{file}' will only insert the first three characters of the sysfs attribute
.\" end of SS subsection "Rules files"
.SH "AUTHOR" .SH "AUTHOR"
.PP .PP
Written by Greg Kroah\-Hartman Written by Greg Kroah\-Hartman

14
udev.xml
View File

@ -3,19 +3,6 @@
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article> <article>
<articleinfo>
<title>xmlto</title>
<author>
<firstname>Kay</firstname>
<surname>Sievers</surname>
<email>kay.sievers@vrfy.org</email>
</author>
<copyright>
<year>2006</year>
<holder>Kay Sievers</holder>
</copyright>
</articleinfo>
<section> <section>
<title>udev</title> <title>udev</title>
<refentry> <refentry>
@ -28,6 +15,7 @@
<refmeta> <refmeta>
<refentrytitle>udev</refentrytitle> <refentrytitle>udev</refentrytitle>
<manvolnum>7</manvolnum> <manvolnum>7</manvolnum>
<refmiscinfo class="version"></refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>

21
udevd.8
View File

@ -1,7 +1,10 @@
.\" ** You probably do not want to edit this file directly ** .\" Title: udevd
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1). .\" Author:
.\" Instead of manually editing it, you probably should edit the DocBook XML .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it. .\" Date: August 2005
.\" Manual: udevd, udevcontrol
.\" Source: udev
.\"
.TH "UDEVD" "8" "August 2005" "udev" "udevd, udevcontrol" .TH "UDEVD" "8" "August 2005" "udev" "udevd, udevcontrol"
.\" disable hyphenation .\" disable hyphenation
.nh .nh
@ -18,24 +21,24 @@ udevd \- event managing daemon
.PP .PP
udevd listens to kernel uevents and passes the incoming events to udev. It ensures the right event order and takes care, that events for child devices are delayed until the parent has finished the device handling. udevd listens to kernel uevents and passes the incoming events to udev. It ensures the right event order and takes care, that events for child devices are delayed until the parent has finished the device handling.
.SH "OPTIONS" .SH "OPTIONS"
.TP .TP 3n
\fB\-\-daemon\fR \fB\-\-daemon\fR
Detach and run in the background. Detach and run in the background.
.TP .TP 3n
\fBlog_priority=\fR\fB\fIvalue\fR\fR \fBlog_priority=\fR\fB\fIvalue\fR\fR
udevcontrol can dynamically set the log level of udevd. Valid values are the numerical syslog priorities or their textual representations: udevcontrol can dynamically set the log level of udevd. Valid values are the numerical syslog priorities or their textual representations:
\fBerr\fR, \fBerr\fR,
\fBinfo\fR \fBinfo\fR
and and
\fBdebug\fR. \fBdebug\fR.
.TP .TP 3n
\fBstop_exec_queue\fR \fBstop_exec_queue\fR
udevcontrol stops the execution of events from udevd. udevcontrol stops the execution of events from udevd.
.TP .TP 3n
\fBstart_exec_queue\fR \fBstart_exec_queue\fR
udevcontrol starts the execution of events from udevd. udevcontrol starts the execution of events from udevd.
.SH "ENVIRONMENT" .SH "ENVIRONMENT"
.TP .TP 3n
\fBUDEV_LOG\fR \fBUDEV_LOG\fR
Overrides the syslog priority specified in the config file. Overrides the syslog priority specified in the config file.
.SH "AUTHOR" .SH "AUTHOR"

14
udevd.xml
View File

@ -3,19 +3,6 @@
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article> <article>
<articleinfo>
<title>xmlto</title>
<author>
<firstname>Kay</firstname>
<surname>Sievers</surname>
<email>kay.sievers@vrfy.org</email>
</author>
<copyright>
<year>2005</year>
<holder>Kay Sievers</holder>
</copyright>
</articleinfo>
<section> <section>
<title>udevd, udevcontrol</title> <title>udevd, udevcontrol</title>
<refentry> <refentry>
@ -28,6 +15,7 @@
<refmeta> <refmeta>
<refentrytitle>udevd</refentrytitle> <refentrytitle>udevd</refentrytitle>
<manvolnum>8</manvolnum> <manvolnum>8</manvolnum>
<refmiscinfo class="version"></refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>

33
udevinfo.8
View File

@ -1,7 +1,10 @@
.\" ** You probably do not want to edit this file directly ** .\" Title: udevinfo
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1). .\" Author:
.\" Instead of manually editing it, you probably should edit the DocBook XML .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it. .\" Date: August 2005
.\" Manual: udevinfo
.\" Source: udev
.\"
.TH "UDEVINFO" "8" "August 2005" "udev" "udevinfo" .TH "UDEVINFO" "8" "August 2005" "udev" "udevinfo"
.\" disable hyphenation .\" disable hyphenation
.nh .nh
@ -11,12 +14,12 @@
udevinfo \- query device information from the udev database udevinfo \- query device information from the udev database
.SH "SYNOPSIS" .SH "SYNOPSIS"
.HP 9 .HP 9
\fBudevinfo\fR [\fB\-q\ \fR\fB\fIquery\-type\fR\fR] [\fB\-a\ \fR] [\fB\-p\ \fR\fB\fIdevice\-path\fR\fR] [\fB\-n\ \fR\fB\fInode\-name\fR\fR] [\fB\-r\fR] [\fB\-e\fR] [\fB\-V\fR] [\fB\-h\fR] \fBudevinfo\fR [\fB\-q\ \fR\fB\fIquery\-type\fR\fR] [\fB\-a\ \fR] [\fB\-p\ \fR\fB\fIdevpath\fR\fR] [\fB\-n\ \fR\fB\fInode\fR\fR] [\fB\-r\fR] [\fB\-e\fR] [\fB\-V\fR] [\fB\-h\fR]
.SH "DESCRIPTION" .SH "DESCRIPTION"
.PP .PP
udevinfo queries the udev database for device information stored in the udev database. It can also query the properties of a device from its sysfs representation to help creating udev rules that match this device. udevinfo queries the udev database for device information stored in the udev database. It can also query the properties of a device from its sysfs representation to help creating udev rules that match this device.
.SH "OPTIONS" .SH "OPTIONS"
.TP .TP 3n
\fB\-q\fR \fB\-q\fR
Query the database for specified type of device data. It needs the Query the database for specified type of device data. It needs the
\fB\-p\fR \fB\-p\fR
@ -28,16 +31,16 @@ to identify the specified device. Valid queries are:
\fBpath\fR, \fBpath\fR,
\fBenv\fR, \fBenv\fR,
\fBall\fR. \fBall\fR.
.TP .TP 3n
\fB\-a\fR \fB\-a\fR
Print all sysfs properties of the specified device that can be used in udev rules to match the specified device. It prints all devices along the chain, up to the root of sysfs that can be used in udev rules. Print all sysfs properties of the specified device that can be used in udev rules to match the specified device. It prints all devices along the chain, up to the root of sysfs that can be used in udev rules.
.TP .TP 3n
\fB\-p \fR\fB\fIdevice\-path\fR\fR \fB\-p \fR\fB\fIdevpath\fR\fR
The sysfs path of the device to query. The devpath of the device to query.
.TP .TP 3n
\fB\-n \fR\fB\fInode\-name\fR\fR \fB\-n \fR\fB\fInode\fR\fR
The name of the device node or a symlink to query The name of the device node or a symlink to query
.TP .TP 3n
\fB\-r\fR \fB\-r\fR
The udev root directory: The udev root directory:
\fI/dev\fR. If used in conjunction with a \fI/dev\fR. If used in conjunction with a
@ -45,10 +48,10 @@ The udev root directory:
or or
\fBsymlink\fR \fBsymlink\fR
query, the query returns the absolute path. query, the query returns the absolute path.
.TP .TP 3n
\fB\-e\fR \fB\-e\fR
Export the content of the udev database. Export the content of the udev database.
.TP .TP 3n
\fB\-h\fR \fB\-h\fR
Print help text. Print help text.
.SH "AUTHOR" .SH "AUTHOR"

14
udevinfo.xml
View File

@ -3,19 +3,6 @@
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article> <article>
<articleinfo>
<title>xmlto</title>
<author>
<firstname>Kay</firstname>
<surname>Sievers</surname>
<email>kay.sievers@vrfy.org</email>
</author>
<copyright>
<year>2005</year>
<holder>Kay Sievers</holder>
</copyright>
</articleinfo>
<section> <section>
<title>udevinfo</title> <title>udevinfo</title>
<refentry> <refentry>
@ -28,6 +15,7 @@
<refmeta> <refmeta>
<refentrytitle>udevinfo</refentrytitle> <refentrytitle>udevinfo</refentrytitle>
<manvolnum>8</manvolnum> <manvolnum>8</manvolnum>
<refmiscinfo class="version"></refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>

13
udevmonitor.8
View File

@ -1,7 +1,10 @@
.\" ** You probably do not want to edit this file directly ** .\" Title: udevmonitor
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1). .\" Author:
.\" Instead of manually editing it, you probably should edit the DocBook XML .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it. .\" Date: August 2005
.\" Manual: udevmonitor
.\" Source: udev
.\"
.TH "UDEVMONITOR" "8" "August 2005" "udev" "udevmonitor" .TH "UDEVMONITOR" "8" "August 2005" "udev" "udevmonitor"
.\" disable hyphenation .\" disable hyphenation
.nh .nh
@ -16,7 +19,7 @@ udevmonitor \- print the kernel and udev event sequence to the console
.PP .PP
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. 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.
.SH "OPTIONS" .SH "OPTIONS"
.TP .TP 3n
\fB\-\-env\fR \fB\-\-env\fR
Print the complete environment for all events. Can be used to compare the kernel supplied and the udev added environment values. Print the complete environment for all events. Can be used to compare the kernel supplied and the udev added environment values.
.SH "AUTHOR" .SH "AUTHOR"

14
udevmonitor.xml
View File

@ -3,19 +3,6 @@
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article> <article>
<articleinfo>
<title>xmlto</title>
<author>
<firstname>Kay</firstname>
<surname>Sievers</surname>
<email>kay.sievers@vrfy.org</email>
</author>
<copyright>
<year>2005</year>
<holder>Kay Sievers</holder>
</copyright>
</articleinfo>
<section> <section>
<title>udevmonitor</title> <title>udevmonitor</title>
<refentry> <refentry>
@ -28,6 +15,7 @@
<refmeta> <refmeta>
<refentrytitle>udevmonitor</refentrytitle> <refentrytitle>udevmonitor</refentrytitle>
<manvolnum>8</manvolnum> <manvolnum>8</manvolnum>
<refmiscinfo class="version"></refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>

15
udevsettle.8
View File

@ -1,7 +1,10 @@
.\" ** You probably do not want to edit this file directly ** .\" Title: udevsettle
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1). .\" Author:
.\" Instead of manually editing it, you probably should edit the DocBook XML .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it. .\" Date: March 2006
.\" Manual: udevsettle
.\" Source: udev
.\"
.TH "UDEVSETTLE" "8" "March 2006" "udev" "udevsettle" .TH "UDEVSETTLE" "8" "March 2006" "udev" "udevsettle"
.\" disable hyphenation .\" disable hyphenation
.nh .nh
@ -16,11 +19,11 @@ udevsettle \- wait until queued kernel/udev events are handled
.PP .PP
Waits watching the udev event queue and exits if all current events are handled. Waits watching the udev event queue and exits if all current events are handled.
.SH "OPTIONS" .SH "OPTIONS"
.TP .TP 3n
\fB\-\-timeout=\fR\fB\fIseconds\fR\fR \fB\-\-timeout=\fR\fB\fIseconds\fR\fR
maximum seconds to wait for the queue to become empty. maximum seconds to wait for the queue to become empty.
.SH "ENVIRONMENT" .SH "ENVIRONMENT"
.TP .TP 3n
\fBUDEV_LOG\fR \fBUDEV_LOG\fR
Overrides the syslog priority specified in the config file. Overrides the syslog priority specified in the config file.
.SH "AUTHOR" .SH "AUTHOR"

14
udevsettle.xml
View File

@ -3,19 +3,6 @@
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article> <article>
<articleinfo>
<title>xmlto</title>
<author>
<firstname>Kay</firstname>
<surname>Sievers</surname>
<email>kay.sievers@vrfy.org</email>
</author>
<copyright>
<year>2006</year>
<holder>Kay Sievers</holder>
</copyright>
</articleinfo>
<section> <section>
<title>udevsettle</title> <title>udevsettle</title>
<refentry> <refentry>
@ -28,6 +15,7 @@
<refmeta> <refmeta>
<refentrytitle>udevsettle</refentrytitle> <refentrytitle>udevsettle</refentrytitle>
<manvolnum>8</manvolnum> <manvolnum>8</manvolnum>
<refmiscinfo class="version"></refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>

11
udevstart.8
View File

@ -1,7 +1,10 @@
.\" ** You probably do not want to edit this file directly ** .\" Title: udevstart
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1). .\" Author:
.\" Instead of manually editing it, you probably should edit the DocBook XML .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it. .\" Date: August 2005
.\" Manual: udevstart
.\" Source: udev
.\"
.TH "UDEVSTART" "8" "August 2005" "udev" "udevstart" .TH "UDEVSTART" "8" "August 2005" "udev" "udevstart"
.\" disable hyphenation .\" disable hyphenation
.nh .nh

14
udevstart.xml
View File

@ -3,19 +3,6 @@
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article> <article>
<articleinfo>
<title>xmlto</title>
<author>
<firstname>Kay</firstname>
<surname>Sievers</surname>
<email>kay.sievers@vrfy.org</email>
</author>
<copyright>
<year>2005</year>
<holder>Kay Sievers</holder>
</copyright>
</articleinfo>
<section> <section>
<title>udevstart</title> <title>udevstart</title>
<refentry> <refentry>
@ -28,6 +15,7 @@
<refmeta> <refmeta>
<refentrytitle>udevstart</refentrytitle> <refentrytitle>udevstart</refentrytitle>
<manvolnum>8</manvolnum> <manvolnum>8</manvolnum>
<refmiscinfo class="version"></refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>

11
udevtest.8
View File

@ -1,7 +1,10 @@
.\" ** You probably do not want to edit this file directly ** .\" Title: udevtest
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1). .\" Author:
.\" Instead of manually editing it, you probably should edit the DocBook XML .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it. .\" Date: August 2005
.\" Manual: udevtest
.\" Source: udev
.\"
.TH "UDEVTEST" "8" "August 2005" "udev" "udevtest" .TH "UDEVTEST" "8" "August 2005" "udev" "udevtest"
.\" disable hyphenation .\" disable hyphenation
.nh .nh

14
udevtest.xml
View File

@ -3,19 +3,6 @@
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article> <article>
<articleinfo>
<title>xmlto</title>
<author>
<firstname>Kay</firstname>
<surname>Sievers</surname>
<email>kay.sievers@vrfy.org</email>
</author>
<copyright>
<year>2005</year>
<holder>Kay Sievers</holder>
</copyright>
</articleinfo>
<section> <section>
<title>udevtest</title> <title>udevtest</title>
<refentry> <refentry>
@ -28,6 +15,7 @@
<refmeta> <refmeta>
<refentrytitle>udevtest</refentrytitle> <refentrytitle>udevtest</refentrytitle>
<manvolnum>8</manvolnum> <manvolnum>8</manvolnum>
<refmiscinfo class="version"></refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>

17
udevtrigger.8
View File

@ -1,7 +1,10 @@
.\" ** You probably do not want to edit this file directly ** .\" Title: udevtrigger
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1). .\" Author:
.\" Instead of manually editing it, you probably should edit the DocBook XML .\" Generator: DocBook XSL Stylesheets v1.70.1 <http://docbook.sf.net/>
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it. .\" Date: March 2006
.\" Manual: udevtrigger
.\" Source: udev
.\"
.TH "UDEVTRIGGER" "8" "March 2006" "udev" "udevtrigger" .TH "UDEVTRIGGER" "8" "March 2006" "udev" "udevtrigger"
.\" disable hyphenation .\" disable hyphenation
.nh .nh
@ -16,14 +19,14 @@ udevtrigger \- request kernel devices events for coldplug
.PP .PP
Trigger kernel device uevents to replay missing events at system coldplug. Trigger kernel device uevents to replay missing events at system coldplug.
.SH "OPTIONS" .SH "OPTIONS"
.TP .TP 3n
\fB\-\-verbose\fR \fB\-\-verbose\fR
print out the devices found in sysfs. print out the devices found in sysfs.
.TP .TP 3n
\fB\-\-dry\-run\fR \fB\-\-dry\-run\fR
don't actually trigger the event. don't actually trigger the event.
.SH "ENVIRONMENT" .SH "ENVIRONMENT"
.TP .TP 3n
\fBUDEV_LOG\fR \fBUDEV_LOG\fR
Overrides the syslog priority specified in the config file. Overrides the syslog priority specified in the config file.
.SH "AUTHOR" .SH "AUTHOR"

14
udevtrigger.xml
View File

@ -3,19 +3,6 @@
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article> <article>
<articleinfo>
<title>xmlto</title>
<author>
<firstname>Kay</firstname>
<surname>Sievers</surname>
<email>kay.sievers@vrfy.org</email>
</author>
<copyright>
<year>2006</year>
<holder>Kay Sievers</holder>
</copyright>
</articleinfo>
<section> <section>
<title>udevtrigger</title> <title>udevtrigger</title>
<refentry> <refentry>
@ -28,6 +15,7 @@
<refmeta> <refmeta>
<refentrytitle>udevtrigger</refentrytitle> <refentrytitle>udevtrigger</refentrytitle>
<manvolnum>8</manvolnum> <manvolnum>8</manvolnum>
<refmiscinfo class="version"></refmiscinfo>
</refmeta> </refmeta>
<refnamediv> <refnamediv>