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

Re: changes in shared svn+ssh repos configuration with fsfs

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2004-07-22 01:36:41 CEST

> I'm wondering if someone can briefly tell me what changes to expect
> in usage of the new fsfs filesystem, with svn+ssh. Specifically,
> will any of the items in "The svn+ssh:// server checklist" as listed
> at http://svnbook.red-bean.com/svnbook/book.html#svn-ch-6-sect-5
> become unnecessary?

In 1.1, both FSFS and BDB repositories will be created with the setgid
bit set on the db directories, so that step will become unnecessary
for any back end. But depending on your primary gid and umask at the
time when you create the repository, you may still need to set the
group ownership and initial permissions appropriately.

With FSFS, it will also be unnecessary to enforce a umask on svn
processes, because FSFS automatically chmods all new rev and rev-prop
files to match the previous ones. (We would, of course, like the
umask issue to go away in BDB as well, but that's waiting for a
possible-far-off BDB enhancement.)

> I used this checklist to set up a shared (BDB) repository. While it
> worked fine, I felt somewhat queasy about directly manipulating a
> repository in this fashion, and I'd feel far more comfortable if
> some (if not all) of these configuration items could be done away
> with eventually.

We've talked about adding --user and/or --group options to the
svnadmin create commands to avoid the need to cross the abstraction
barrier during initial setup, but there's been no strong consensus on
those one way or the other.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 22 01:37:19 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.