s6

commit 928bea7eec8bcfe1abbf8ac2fe01a65fe31a9ed0
parent 384fa7f25cb8e9d759d8aaa681aa98e57d60dfac
Author: Laurent Bercot <ska-skaware@skarnet.org>
Date:   Fri, 25 Dec 2015 18:26:12 +0000

 fix references to s6-ipcserver (thanks Casper Ti. Vector)

Diffstat:
M
doc/s6-log.html
 | 
4
+---
M
doc/ucspilogd.html
 | 
2
+-

2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/doc/s6-log.html b/doc/s6-log.html
@@ -457,9 +457,7 @@ caught by this syslogd service are not part of the logging chain.
  It is probably overkill to provide the syslogd service with its own
 logger; error messages from syslogd can default to the catch-all logger.
  The s6 package, including the <a href="ucspilogd.html">ucspilogd</a> program,
-combined with the
-<a href="http://skarnet.org/software/s6-networking/">s6-networking</a>
-package, provides enough tools to easily implement
+provides enough tools to easily implement
 a complete syslogd system, for a small fraction of the resource needs and
 the complexity of native syslogd implementations. </li>
 </ul>
diff --git a/doc/ucspilogd.html b/doc/ucspilogd.html
@@ -61,7 +61,7 @@ components:
 
 <ul>
  <li> A Unix stream super-server such as
-<a href="http://skarnet.org/software/s6-networking/s6-ipcserver.html">s6-ipcserver</a>
+<a href="s6-ipcserver.html">s6-ipcserver</a>
 listening to the Unix domain socket <tt>/dev/log</tt>, to connect to
 the kernel log-reading interface. </li>
  <li> <tt>ucspilogd</tt> running under that super-server, to read the