Re: What Permissions Are Needed For SVN Commit

On 19/07/07, joseph.h.dayney@rrd.com <joseph.h.dayney@rrd.com> wrote:
> 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 ?
>
> First we were getting permission errors on "mkdir " in the
> ./db/transaction/1818-1.txn
>
> We thought it was that svnadm did NOT have permission to write to the
> Directory ... so they changed the explicit Rule
>
> Now it is failing on trying to do a chmod one level down (so I guess mkdir
> is now working) ./db/transaction/1818-a.txn/rev
>
> Is there any documentation showing what the process does, step by step on
> commits or other writes so that we can see exactly what permissions are
> required so that we can modify the permission rulesets in this Tool and get
> beyond these errors ?

You need to ask this question on the subversion users list. This is a
server problem.

I don't understand why your admins feel the need to restrict the
svnadm user at all within the repository directories. It needs full
control AFAIK

Simon

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org