From 3a226af83a34d7b92492df77511f43dc9f5e33aa Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Tue, 23 May 2017 11:04:09 +0000 Subject: Switch doc to schemeless URLs --- doc/skadns/skadnsd.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'doc/skadns/skadnsd.html') diff --git a/doc/skadns/skadnsd.html b/doc/skadns/skadnsd.html index 0a11297..951dfb8 100644 --- a/doc/skadns/skadnsd.html +++ b/doc/skadns/skadnsd.html @@ -6,14 +6,14 @@ s6-dns: the skadnsd internal program - + libskadns
s6-dns
-Software
-skarnet.org

The `skadnsd` program

@@ -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. +s6-ipcserver. skadnsd follows the UCSPI interface, it can be directly executed from the superserver.

@@ -98,14 +98,14 @@ 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. -It follows skalibs' +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 using a skadnsd service) under a program like -s6-softlimit to +s6-softlimit to set a memory limit to every skadnsd instance. If skadnsd runs out of allowed memory, it will simply die.
If you're using a skadnsd service: you should configure your -- cgit v1.3.1

The skadnsd program

The `skadnsd` program