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

Failure when attempting to lock a file: Can't chmod

From: Jeremy Statz <jstatz_at_pistudios.com>
Date: 2006-12-01 09:24:55 CET

I'm attempting (using TortoiseSVN) to lock a file on our SVN server, but
whenever I request a lock I get an error reading "Can't chmod
'/usr/raid/subversion/db/locks/458': Operation not permitted. I've
gathered from various google searches than the db/locks folder needs to
be made writable, but even setting its permissions to 777 doesn't fix
the problem -- the subfolders that SVN attempts to create within it end
up read-only and (apparently) subversion is failing to change these
permissions.

Currently we have a user called "svn" that has ownership of this folder
tree and all access goes through this user. Is there something special
we have to set to allow this user to use chmod? Are we missing
something obvious here?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 1 16:21:38 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.