On 7/19/07, joseph.h.dayney@rrd.com <joseph.h.dayney@rrd.com> wrote:
>
> Guys,
>
> We are trying to DEBUG some permissions problems on a Sun Solaris UNIX
> Server. The Powers that be are trying to implement a Tool from CA called
> Access Control ... think its like ACL (Access Control Lists) and we are
> having problems with Subversion commits.
>
> The Subversion Administrative ID is " svnadm "
>
>
> QUESTION:
>
> When a User tries to commit a change to the Subversion Repository, is it the
> Subversion Adminstrative ID that is actually try to execute the commands ?
That depends. Are you using svn://, svn+ssh://, http:// or file://
access? If it's svn:// or http://, then whatever ID svnserve or Apache
runs under is what needs the permissions. If it's file://, it's the
user ID which is actually doing the commit. I have no experience with
svn+ssh, so I'm not sure what's up there.
Your best option is to grant the ID under which the server process
runs fill control over the repository directory.
Like Simon said, you'll need to ask on the SVN users list.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Sat Jul 21 17:52:37 2007