[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Somewhat corrupted repository: Berkeley DB Permissions errors on SVN 1.0.2

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-05-26 21:51:23 CEST

On Wed, 2004-05-26 at 14:48, Paul Oppenheim wrote:

> The current permissions and access system is very confusing to those
> who are developers, not unix sysadmin gurus. As it is, svn+ssh does not
> work correctly out of the box. Why does it work the way it currently
> does (that is, designed to ignore that it needs some type of umask
> intervention), and is there change in the wind? Do I have to do the
> somewhat dodgy umask shuffle, or is there another way?

There's no other way. svn+ssh:// isn't for the faint-hearted. There's
no magic way to make it "work out of the box".

CVS has similar problems out-of-the-box, assuming you have a bunch of
system users all reading/writing RCS files. It's just the natural
side-effect of a bunch of users trying to directly access database

The only "clean solution" is to allow a *single* process to own and
access the database.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 26 21:57:09 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.