From fc460fbd498736de9b2674acb0383b2e2bffa0f2 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Sat, 25 Sep 2021 23:45:38 +0000
Subject:  More doc fixes

Signed-off-by: Laurent Bercot <ska@appnovation.com>
---
 doc/nsssd-switch.html | 15 +++++++++++++--
 1 file changed, 13 insertions(+), 2 deletions(-)

(limited to 'doc')

diff --git a/doc/nsssd-switch.html b/doc/nsssd-switch.html
index 3b86f1a..462b445 100644
--- a/doc/nsssd-switch.html
+++ b/doc/nsssd-switch.html
@@ -29,10 +29,21 @@ the <a href="libnsss/nsss-switch.html">nsss-switch</a> functions.
  The <tt>nsssd-switch</tt> backend is the real point of the <a href="index.html">nsss</a>
 package: it allows a complex configuration using different other backends,
 similarly to the <a href="nsswitch.html">/etc/nsswitch.conf</a> mechanism
-but without its drawbacks. It accomplishes this by reading its backend
-configuration on the command line.
+but without its drawbacks:
 </p>
 
+<ul>
+ <li> Backends that access the user/group/shadow databases are not implemented
+via dynamically loaded shared libraries, but executables that are spawned by
+<tt>nsssd-switch</tt>. The executables use the same protocol as <tt>nsssd-switch</tt>
+itself, so the provided <a href="nsssd-unix.html">nsssd-unix</a> and
+<a href="nsssd-nslcd.html">nsssd-nslcd</a> programs can be used as backends. </li>
+ <li> No configuration file is needed, so no parsing is necessary. Backends
+are sequentially listed on the <tt>nsssd-switch</tt> command line, along with
+a single argument telling <tt>nsssd-switch</tt> what to do in case of failure.
+This makes the decision automaton very simple. </li>
+</ul>
+
 <h2> Interface </h2>
 
 <pre>
-- 
cgit v1.2.3