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

RE: Is FSFS better with svn+ssh?

From: HAND,Nathan <Nathan.HAND_at_dewr.gov.au>
Date: 2004-11-30 01:18:39 CET

> -----Original Message-----
> From: Wade Williams [mailto:wadesworld@mac.com]
> Sent: Tuesday, November 30, 2004 11:05 AM
> To: users@subversion.tigris.org
> Subject: Is FSFS better with svn+ssh?
> Do the guidelines described in "Supporting Multiple Repository Access
> Methods":
> http://svnbook.red-bean.com/en/1.1/ch06s05.html
> apply equally to FSFS repositories? That is, is FSFS a better choice
> with svn+ssh or do all the same caveats still apply?

Yes, all of the "same caveats" still apply. The short list (these
are explained in more detail at your URL) of best practises.

  - wrapping the svn and svnserve binaries with a script that
    sets the umask to 002
  - all files and directories under the repository are in the
    subversion group with permissions ug+rw
  - all directories under the repository have the setgid bit;
    find repository -type d -exec chmod g+s {} \;
  - all users requiring write access belong to the subversion
  - don't backup the repository; dump it somewhere and backup
    the dump instead

Missing any of those steps results in pain, no matter whether I'm
using BDB or FSFS.

The information contained in this e-mail message and any attached files may
be confidential information, and may also be the subject of legal
professional privilege. If you are not the intended recipient any use,
disclosure or copying of this e-mail is unauthorised. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete all copies of this transmission together with any attachments.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 30 01:20:50 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.