summary refs log tree commit diff
path: root/doc/s6-uevent-listener.html
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2017-10-26 14:03:33 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2017-10-26 14:03:33 +0000
commitbc81629c44b0083efa18ef11b653890a3c283645 (patch)
treee71c8a674688d9c50a265a1b79b65b6959ba8631 /doc/s6-uevent-listener.html
parentafba22c15cf2894eade816c87574ba02bc85c1da (diff)
downloads6-linux-utils-bc81629c44b0083efa18ef11b653890a3c283645.tar.gz
s6-linux-utils-bc81629c44b0083efa18ef11b653890a3c283645.tar.xz
s6-linux-utils-bc81629c44b0083efa18ef11b653890a3c283645.zip
Deprecate s6-uevent-*, prepare for 2.4.0.2
Diffstat (limited to 'doc/s6-uevent-listener.html')
-rw-r--r--doc/s6-uevent-listener.html16
1 files changed, 12 insertions, 4 deletions
diff --git a/doc/s6-uevent-listener.html b/doc/s6-uevent-listener.html
index 73bad1d..cd60639 100644
--- a/doc/s6-uevent-listener.html
+++ b/doc/s6-uevent-listener.html
@@ -5,7 +5,7 @@
     <meta http-equiv="Content-Language" content="en" />
     <title>s6-linux-utils: the s6-uevent-listener program</title>
     <meta name="Description" content="s6-linux-utils: the s6-uevent-listener program" />
-    <meta name="Keywords" content="s6 linux administration root utilities devd mdev udev s6-uevent-listener uevent" />
+    <meta name="Keywords" content="s6 linux administration root utilities devd mdev mdevd udev s6-uevent-listener uevent" />
     <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> -->
   </head>
 <body>
@@ -24,6 +24,14 @@
 its standard output, using a simple format.
 </p>
 
+<p>
+<strong>This program is deprecated</strong>, and will disappear in a
+near future version of s6-linux-utils. It has been replaced with the
+<a href="//skarnet.org/software/mdevd/mdevd-netlink.html">mdevd-netlink</a>
+program, from the <a href="//skarnet.org/software/mdevd/">mdevd</a>
+package.
+</p>
+
 <h2> Interface </h2>
 
 <pre>
@@ -38,7 +46,7 @@ null characters, so a terminal will not display them correctly. To
 properly use s6-uevent-listener, it should be piped into a handler
 program such as
 <a href="s6-uevent-spawner.html">s6-uevent-spawner</a>.
-<!-- or <a href="mdevd.html">mdevd</a>. --> </li>
+or <a href="//skarnet.org/software/mdevd/mdevd.html">mdevd</a>. </li>
  <li> s6-uevent-listener is a long-lived program.
 When it receives a SIGTERM, it stops listening; it will
 exit as soon as it has flushed its event queue to stdout. </li>
@@ -93,12 +101,12 @@ only program handling uevents, which means that
  <li> Examples of valid uses of s6-uevent-listener:
   <ul>
    <li> <tt>s6-uevent-listener | s6-uevent-spawner mdev</tt> </li>
-<!--   <li> <tt>s6-uevent-listener | mdevd</tt> </li> -->
+   <li> <tt>s6-uevent-listener | mdevd</tt> </li>
    <li> Those examples can be made safer by using a supervision system:
 under <a href="//skarnet.org/software/s6/">s6</a> or
 <a href="//skarnet.org/software/s6-rc/">s6-rc</a>, write a service
 pipeline where <tt>s6-uevent-listener</tt> is a producer and
-<tt>s6-uevent-spawner mdev</tt> <!-- or <tt>mdevd</tt> --> is a consumer. This
+<tt>s6-uevent-spawner mdev</tt> or <tt>mdevd</tt> is a consumer. This
 setup has the advantage, among others, that you can restart the netlink
 listener and the event handler separately. </li>
   </ul>