From e969f9b508ed06984da48f61c7816a9b9b40409b Mon Sep 17 00:00:00 2001
From: Tero Saarni <tero.saarni@est.tech>
Date: Mon, 29 Mar 2021 18:57:53 +0300
Subject: [PATCH 234/238] ITS#9468 documented that re-connecting does not
 happen after idle-timeout or conn-ttl

---
 doc/man/man5/slapd-ldap.5 | 20 ++++++++++++++++----
 1 file changed, 16 insertions(+), 4 deletions(-)

diff --git a/doc/man/man5/slapd-ldap.5 b/doc/man/man5/slapd-ldap.5
index 1c509542f..6088b049b 100644
--- a/doc/man/man5/slapd-ldap.5
+++ b/doc/man/man5/slapd-ldap.5
@@ -193,8 +193,12 @@ underlying libldap, with rebinding eventually performed if the
 
 .TP
 .B conn\-ttl <time>
-This directive causes a cached connection to be dropped and recreated
-after a given ttl, regardless of being idle or not.
+This directive causes a cached connection to be dropped after a given ttl,
+regardless of being idle or not.  If a client connection outlives the remote
+connection, the client will receive
+.IR LDAP_UNAVAILABLE
+when it executes the next operation.
+
 
 .TP
 .B idassert\-authzFrom <authz-regexp>
@@ -410,8 +414,11 @@ for details on the syntax of this field.
 
 .TP
 .B idle\-timeout <time>
-This directive causes a cached connection to be dropped an recreated
-after it has been idle for the specified time.
+This directive causes a cached connection to be dropped after it has been idle
+for the specified time.  If a client connection outlives the remote connection,
+the client will receive
+.IR LDAP_UNAVAILABLE
+when it executes the next operation.
 
 .TP
 .B keepalive  <idle>:<probes>:<interval>
@@ -518,6 +525,11 @@ or when chasing a referral, if
 .B chase\-referrals
 is set to
 .IR yes .
+Note, however, that connection is not re-established automatically after it
+was dropped due to
+.B idle\-timeout
+or
+.B conn\-ttl .
 
 .TP
 .B session\-tracking\-request {NO|yes}
-- 
2.32.0