Re: Repository access woes

%% John Peacock <jpeacock@rowman.com> writes:

  jp> The fact that _you_ have had no problems with CVS on an NFS
  jp> partition doesn't count for much. You may have been lucky so far
  jp> (low concurrency CVS repository?). The strong recomendation has
  jp> always been (AFAIK) to not mix CVS and NFS, no matter what O/S you
  jp> are talking about.

Hm. I wonder if there's been a misunderstanding.

When Marcus talks about CVS via NFS I assumed he meant that people were
using a CVS server to access the repository, but that the repository
lives on an NFS-mounted partition rather than on the server's local
disk.

If true, then this is of course a common, supported environment that
will work, and if SVN doesn't support this (esp. with the larger
repository sizes it apparently generates) then this is likely an issue
for any large-scale SVN use.

If Marcus was talking about a CVS repository shared via NFS where
everyone runs CVS operations directly on the repository rather than
through a server, then John is quite correct: that is a known bad
configuration and you won't find any CVS expert-types (at least I never
heard of any) who would say that was a reliable configuration. It may
work "most of the time" by chance, but ...

So, I guess we need to define the environment more completely.

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <psmith@nortelnetworks.com>   HASMAT--HA Software Mthds & Tools
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
   These are my opinions---Nortel Networks takes no responsibility for them.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org