--On Friday, March 7, 2003 5:08 PM -0500 Michael Price <mprice@atl.lmco.com>
wrote:
> Just a little heads up to people running the latest CVS apache rather
> than a release.
>
> If you see errors like:
>
> [Fri Mar 07 16:37:59 2003] [error] [client 127.0.0.1] The lock database
> could not be opened, preventing access to the various lock properties
> for the PROPFIND. [500, #0]
> [Fri Mar 07 16:37:59 2003] [error] [client 127.0.0.1] A lock database
> was not specified with the DAVGenericLockDB directive. One must be
> specified to use the locking functionality. [500, #401]
>
> in your error log then you specified --enable-dav-lock and should
> disable that.
That's why you have to explicitly enable mod_dav_lock. If you don't know what
something does, don't enable it.
mod_dav_lock is experimental, but it serves a purpose for Subversion admins
who want to provide service to Class 2 DAV clients. I'd like to make it so
that it is a bit saner, but that requires tweaking mod_dav and how it queries
locking providers (must query for lock at the resource level rather than at
the provider level). And, that's really low on my todo list since I'd have to
do it in such a way that doesn't break existing mod_dav modules. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Mar 9 19:06:06 2003