DBDPersist takes On or Off

reported by Phil Endecott
note odd DBDPersist format in 2.2.0 and 2.2.1

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@569109 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_dbd.xml b/docs/manual/mod/mod_dbd.xml
index 747d04f3aaf95b2b7a57b77c7129053a24cffe1a..e8c9e4c8fdee8e51d762e68a718dd99a69144f3e 100644 (file)
--- a/docs/manual/mod/mod_dbd.xml
+++ b/docs/manual/mod/mod_dbd.xml
@@ -155,12 +155,12 @@ APR_DECLARE_OPTIONAL_FN(void, ap_dbd_prepare, (server_rec*, const char*, const c
 <directivesynopsis>
 <name>DBDPersist</name>
 <description>Whether to use persistent connections</description>
-<syntax>DBDPersist 0|1</syntax>
+<syntax>DBDPersist On|Off</syntax>
 <contextlist><context>server config</context><context>virtual host</context>
 </contextlist>
 
 <usage>
-    <p>If set to 0, persistent and pooled connections are disabled.
+    <p>If set to Off, persistent and pooled connections are disabled.
     A new database connection is opened when requested by a client,
     and closed immediately on release.  This option is for debugging
     and low-usage servers.</p>
@@ -168,6 +168,10 @@ APR_DECLARE_OPTIONAL_FN(void, ap_dbd_prepare, (server_rec*, const char*, const c
     <p>The default is to enable a pool of persistent connections
     (or a single LAMP-style persistent connection in the case of a
     non-threaded server), and should almost always be used in operation.</p>
+
+    <p>Prior to version 2.2.2, this directive accepted only the values
+    <code>0</code> and <code>1</code> instead of <code>Off</code> and
+    <code>On</code>, respectively.</p>
 </usage>
 </directivesynopsis>