1
1
mirror of https://github.com/systemd/systemd-stable.git synced 2025-01-15 23:24:12 +03:00

add missing udevsend man page

Signed-off-by: Kay Sievers <kay.sievers@suse.de>
This commit is contained in:
Kay Sievers 2005-08-31 00:00:22 +02:00
parent 7b86ada7d4
commit 0599b4a25f
2 changed files with 128 additions and 0 deletions

90
docs/udevsend.xml Normal file
View File

@ -0,0 +1,90 @@
<?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>
<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>
<title>udevsend</title>
<refentry>
<refentryinfo>
<title>udevsend</title>
<date>August 2005</date>
<productname>udev</productname>
</refentryinfo>
<refmeta>
<refentrytitle>udevsend</refentrytitle>
<manvolnum>8</manvolnum>
</refmeta>
<refnamediv>
<refname>udevsend</refname>
<refpurpose>send the current environment to the udev daemon</refpurpose>
</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
<command>udevsend</command>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1><title>DESCRIPTION</title>
<para>Usually the udev daemon listens directly to the kernel uevents.
udevsend may be used to pass events for already existing devices from
a userspace application to the daemon.</para>
</refsect1>
<refsect1><title>ENVIRONMENT</title>
<variablelist>
<varlistentry>
<term><option>ACTION</option></term>
<listitem>
<para><replaceable>add</replaceable> or <replaceable>remove</replaceable> signifies
the addition or the removal of a device.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>DEVPATH</option></term>
<listitem>
<para>The sysfs devpath without the mountpoint but a leading slash.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>SUBSYSTEM</option></term>
<listitem>
<para>The kernel subsystem the device belongs to.</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>8</manvolnum>
</citerefentry>,
<citerefentry>
<refentrytitle>udevd</refentrytitle><manvolnum>8</manvolnum>
</citerefentry></para>
</refsect1>
</refentry>
</section>
</article>

38
udevsend.8 Normal file
View File

@ -0,0 +1,38 @@
.\" ** You probably do not want to edit this file directly **
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.0).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
.TH "UDEVSEND" "8" "August 2005" "udev" "udevsend"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.SH "NAME"
udevsend \- send the current environment to the udev daemon
.SH "SYNOPSIS"
.HP 9
\fBudevsend\fR
.SH "DESCRIPTION"
.PP
Usually the udev daemon listens directly to the kernel uevents. udevsend may be used to pass events for already existing devices from a userspace application to the daemon.
.SH "ENVIRONMENT"
.TP
\fBACTION\fR
\fIadd\fR
or
\fIremove\fR
signifies the addition or the removal of a device.
.TP
\fBDEVPATH\fR
The sysfs devpath without the mountpoint but a leading slash.
.TP
\fBSUBSYSTEM\fR
The kernel subsystem the device belongs to.
.SH "AUTHOR"
.PP
Written by Kay Sievers
<kay.sievers@vrfy.org>.
.SH "SEE ALSO"
.PP
\fBudev\fR(8),
\fBudevd\fR(8)