Hello,
1. What is the right method of setting up permissions for using
Subversion on a local filesystem with local users (Unix environment, of
course)? I have had some serious problems with many different
arrangments.
Right now, I have the repository owned and created by user svn, and all
users and the user svn are in the same group. The svn binaries are *not*
setuid svn (which creates its own set of problems). In order to get
things to work properly I have to set the umask for the users to allow
group write permissions since when users do certain svn operations (like
commits) they create files *in the repository dir* (for example the
db/log.00000000xx files) that are *owned by the user* and these files must
be writable by other users when they do subsequent svn operations. Is
this how things should be set up? I am uncomfortable that all users have
to have g+w in their umask, since it makes not only the repository
modifiable by all (which is inevitable of course) but also any files that
the users creates for other purposes. Also, I'm concerned that these
files in the repository are owned by other users may cause a problem when
some sort of database consolidation takes place and svn tries to delete
those files. Is this a concern?
2. More generally, is using Subversion with local users on the local
filesystem (not remotely via http or whatever) supported very well, or are
the remote access methods the only ones that work reliably? I have had
lots of database lockup problems in the past and I'm not sure they are all
going to go away now that I have the issue in #1 worked out with group
write permission enabled in the users' umasks . . .
Thanks,
Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 12 05:55:55 2002