On Thursday 10 March 2005 7:48 pm, Allie D wrote:
> I have a subversion respository that has multiple users by using group
> perms with svnserve. I really want to post a web interface for browsing
> purposes only...so websvn fits the bill perfectly. The only problem is that
> unless I make the the apache user (www) own the subversion repository
> websvn breaks and errors "permission denied" on the DB dip. Well when I
> change the owner of the repository it breaks commandline access...catch 22
> ;) So, I run svnserve as an "svn" user...and my next step was to change the
> group to svn (different group than users) to hopefully fix it. Is this the
> right attack to fix this or am I going down the wrong path ???? Any help
> would be awesome...I'm sick of CVS and really want this work ;)
I tried this, but ended up with I think umask problems. I made the apache
user part of the svn group, set all the repo files to owner svn, group svn
with 664 permissions and the db directory g+s. However, the apache module
would create the log files with permission 600 (the group was svn though).
svnserve would complain about a broken db, because there were unreadable
(non-writeable?) log files.
This scenario is approximate, since it was a while ago, but the outcome was
that WEB updates broke the svnserve access, and would have been fixable if I
could have found a umask option for the webdav(?) module. I have not tried
it with fsfs, only the dbfs.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 11 18:38:33 2005