From: Chris Darroch Date: Thu, 23 Aug 2007 18:35:10 +0000 (+0000) Subject: DBDPersist takes On or Off X-Git-Tag: 2.2.6~134 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7d989a5bbb5cf81cf6aa2df8727cf2c24e2c5723;p=thirdparty%2Fapache%2Fhttpd.git 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 747d04f3aaf..e8c9e4c8fde 100644 --- 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 DBDPersist Whether to use persistent connections -DBDPersist 0|1 +DBDPersist On|Off server configvirtual host -

If set to 0, persistent and pooled connections are disabled. +

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.

@@ -168,6 +168,10 @@ APR_DECLARE_OPTIONAL_FN(void, ap_dbd_prepare, (server_rec*, const char*, const c

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.

+ +

Prior to version 2.2.2, this directive accepted only the values + 0 and 1 instead of Off and + On, respectively.