Garrett Rooney wrote:
>On Thu, Apr 18, 2002 at 01:35:53PM -0400, Scott Lenser wrote:
>
>>>As I see CVS used around here there are 3 basic use cases.
>>>
>>>1) private repository accessed on local storage
>>>
>>>CVS does this, SVN does this. Although am I right in thinking that the use of
>>>db means you'd have problems if this was nfs mounted storage? If so this is
>>>rather limiting for people whose $HOME is network mounted.
>>>
>>I'd put the network mounted storage into use case 2. I've seen many CVS
>>repositories that are shared amongst a group of people simply by putting
>>the repository storage on a networked file system like AFS. This gives
>>reasonable performance and the filesystem already has all the permission
>>mechanisms built in. This is a pretty convenient way to share a repository
>>but isn't really necessary as long as there is a convenient way to handle
>>use case 2.
>>
>
>right now, we don't work correctly on NFS at all. berkeley db does
>not function correctly on an NFS filesystem, so if that's needed,
>we're talking about rewriting the underlying filesystem, and i don't
>think anyone is jumping up to do that anytime soon...
>
As a matter of fact, CVS can't be used safely over NFS either, because
of locking issues. This is IIRC explicitly stated in the CVS manual,
which recommends using pserver even for case 2. True, you don't often
see the problem, but I've heard enough horror stories about silently
corrupted CVS repositories that I tend to believe the docs.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 18 23:09:45 2002