changes in shared svn+ssh repos configuration with fsfs

Dear People,

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?

This one

"When BerkeleyDB creates new logfiles, they need to be owned by the
group as well, so make sure you run chmod g+s on the repository's db
directory."

at least, hopefully?

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.

Please cc me on any reply, I'm not subscribed. Thanks.

                                                              Faheem.

---------------------------------------------------------------------
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:08:50 2004