On Jun 5, 2007, at 11:57, Bob Aiello wrote:
>>> For a linux based FSFS repository, what are
>>> the minimum permissions required for access
>>> by members of a group?
>>
>> I use the following
>>
>> # cd /var/svn
>> # svnadmin create /var/svn/reposname
>> # chmod -R 770 reposname
>> # chmod -R g+s reposname/db
>> # chown -R owner:svngroup reposname
>>
>> I then assign all users to "svngroup" which gives them read-write
>> access
>>
>> to the repository. We don't do path-based authentication (yet) or
>> use
>> any other access method other then svn+ssh.
>
> Hmmm... what is the purpose of setting the s bit
> on the db for group?
>
> chmod -R g+s reposname/db
Presumably he's doing that because the book says to:
http://svnbook.red-bean.com/en/1.2/svn.serverconfig.multimethod.html
> Another common problem is often encountered on Unix-like systems.
> As a repository is used, Berkeley DB occasionally creates new log
> files to journal its actions. Even if the repository is wholly
> owned by the svn group, these newly created files won't necessarily
> be owned by that same group, which then creates more permissions
> problems for your users. A good workaround is to set the group SUID
> bit on the repository's db directory. This causes all newly-created
> log files to have the same group owner as the parent directory.
Granted, that does mention BDB-bases repositories specifically.
Perhaps this is not necessary for FSFS-based repositories. I don't know.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 5 19:36:30 2007