From: Joshua Slive In addition, a location for the DAV lock database must be
specified in the global section of your httpd.conf
- file:DavLockDB
+ directive:
The directory containing the lock database file must be
writable by the
DavLockDB /usr/local/apache2/var/DavLock
@@ -74,12 +75,7 @@
User
and Group under which
- Apache is running. For security reasons, you should create a
- directory for this purpose rather than changing the permissions on
- an existing directory. In the above example, Apache will create
- files in the /usr/local/apache2/var/ directory
- with the base filename DavLock and extension name
- chosen by the server.
You may wish to add a <Limit> clause inside the <Location> directive to limit access to
DAV-enabled locations. If you want to set the maximum amount of
@@ -89,7 +85,7 @@
requests.
In addition, a location for the DAV lock database must be
specified in the global section of your
- DavLockDB /tmp/DavLock
+ DavLockDB /usr/local/apache2/var/DavLock
<Location /foo>
diff --git a/docs/manual/mod/mod_dav.xml b/docs/manual/mod/mod_dav.xml
index fc8abf5ec85..286931c119a 100644
--- a/docs/manual/mod/mod_dav.xml
+++ b/docs/manual/mod/mod_dav.xml
@@ -35,7 +35,8 @@
httpd.conf
- file:
The directory containing the lock database file must be
writable by the /usr/local/apache2/var/ directory
- with the base filename DavLock and extension name
- chosen by the server.
You may wish to add a The directory containing the lock database file must be
+ writable by the
+ DavLockDB /usr/local/apache2/var/DavLock
<Location /foo>
Example
- DavLockDB logs/DavLock
+ DavLockDB var/DavLock
User
+ and Group under which
+ Apache is running. For security reasons, you should create a
+ directory for this purpose rather than changing the permissions on
+ an existing directory. In the above example, Apache will create
+ files in the var/ directory under the ServerRoot with the base filename
+ DavLock and extension name chosen by the server.