[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Lock file command not working

From: Trahan, Ted <edward.trahan_at_medtronic.com>
Date: 2007-01-12 20:10:01 CET

> Problem: I am able to read and write to the project in the repository.
> However, executing a file-lock command returns
> "Error: Lock request failed: 405 Method Not Allowed (http://mydomain)"
>
> I get the same error using both TSVN and (as a sanity check) svn.exe.
>
> The permissions on the server's /home/svn/<repos>/locks directory are
> the same as other repository directories (conf/, hooks/, etc).
>

Since my original post I have made the following additional
observations:

No errors related to the request for a file lock appear in the apache
error_log. So it would seem that apache is not getting in the way.

From perusal of Subversion resources on the web, it appears that file
locking functionality was introduced with Subversion 1.2.1. We are
using rev 1.3.2, so presumably the version of Subversion we are using
supports the lock-file feature.

Looking in the locks/ directory I see "db.lock" and "db-logs.lock"
files. These seem to be specific to Berkley database repositories. I
am using a FSFS file structure. The Subversion book talks about lock
files and
lock tokens, all of which makes sense when file locking works. I
haven't been able to capitalize on that information to figure out why
I get the file lock message.

Again, I would be grateful for your ideas.

Thanks again for your consideration.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 12 20:10:23 2007

This is an archived mail posted to the Subversion Users mailing list.