From 52545ad7f5752160277cc1645340e863fd8bb3a2 Mon Sep 17 00:00:00 2001
From: Laurent Bercot
Date: Sun, 14 Dec 2014 10:10:40 +0000
Subject: skadnsd doc update
---
doc/skadns/skadnsd.html | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
(limited to 'doc/skadns/skadnsd.html')
diff --git a/doc/skadns/skadnsd.html b/doc/skadns/skadnsd.html
index e8316b8..16e1c38 100644
--- a/doc/skadns/skadnsd.html
+++ b/doc/skadns/skadnsd.html
@@ -18,9 +18,9 @@
skadnsd is the skadns daemon. It reads a series of
-queries from the client on stdin, resolves them asynchronously,
-and writes
-the answers to the client as soon as it gets them. It exits 0
+queries from the client its stdin socket, resolves them asynchronously,
+and sends
+the answers back to the client as soon as it gets them. It exits 0
when its stdin closes. It exits 111 on any serious error,
writing the error message to stderr.
@@ -80,7 +80,7 @@ that it requires support from the system administrator.
skadnsd has no "standalone" mode: it is designed to work with a Unix
domain superserver, like
s6-ipcserver.
-skadnsd follows the UCSPI"
+skadnsd follows the UCSPI
interface, it can be directly executed from the superserver.
@@ -96,7 +96,10 @@ to run it under a specific account.
- Users should never invoke skadnsd directly. It's an
-internal program designed to be spawned by the skadns library.
+internal program designed to be spawned by the skadns library.
+It follows skalibs'
+"skaclient" protocol and is unusable unless spawned by the right client
+library also using that protocol.
- If a poorly designed client sends a lot of queries and never reads the
answers, those will indefinitely queue up in the daemon, eating up
memory. You should run your process (or your Unix superserver, if you're
--
cgit v1.2.3