Apache Module mod_dav_lock

This module implements a generic locking API which can be used by any backend provider of

. It mod_davrequires at least the service of

. But without a backend provider which makes use of it, it's useless and should not be loaded into the server. A sample backend module which actually utilizes mod_dav

is moddavlockmoddavsvn, the subversion provider module.

does moddavfsnot need this generic locking module, because it uses its own more specialized version.

In order to make

functional, you just have to specify the location of the lock database using the moddavlock

directive described below.DavGenericLockDB

In order to retrieve the pointer to the locking provider function, you have to use the aplookupprovider

API with the arguments dav-lock

directive to specify the full path to the lock database, excluding an extension. If the path is not absolute, it will be interpreted relative to

. The implementation of ServerRoot

uses a SDBM database to track user locks.moddavlock

The directory containing the lock database file must be writable by the

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 Groupvar/

with the base filename ServerRootDavLock

Modules | Directives | FAQ | Glossary | Sitemap

Apache HTTP Server Version 2.4