for now, mention that the TTL isn't tracking to the last I/O on the LDAP conn.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1452865 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_ldap.xml b/docs/manual/mod/mod_ldap.xml
index 09af6324208811e86bf6612df74c48a26bf4c79d..bbc9f2db55a37915b5105f20d4da9aaa437e24b1 100644 (file)
--- a/docs/manual/mod/mod_ldap.xml
+++ b/docs/manual/mod/mod_ldap.xml
@@ -736,6 +736,11 @@ connection client certificates.</description>
     connection pool.  The default value of -1, and any other negative value,
      allows connections of any age to be reused.</p>
 
+    <p>The timemout is based on when the LDAP connection is returned to the 
+    pool, not based on the last time I/O has been performed over the backend
+    connection.  If the information is cached, the apparent idle time can exceed
+    the <directive>LDAPConnectionPoolTTL</directive>. </p> 
+
     <note><p>This timeout defaults to units of seconds, but accepts
     suffixes for milliseconds (ms), minutes (min), and hours (h).
     </p></note>