On Wed, Jul 9, 2008 at 10:29 PM, Smith, Michelle <
> I'm using Subversion for Win32, version 1.4.5
> We've been using Subversion (using the SVNSERVE.EXE running as a Windows
> service) for a team of 5 people to manage version control. Due to huge file
> sizes, we're about to shift across to a dedicated SAN with massive storage
> volume. The WinXP desktop machine that is currently running the
> SVNSERVE.EXE service will be taken off-line.
> The SAN storage space (mapped to "Y:\" on my machine) does NOT have the
> SVNSERVE.EXE running as a service since it's apparently just an array of
> hard drives without an operating system. My client machine doesn't have the
> SVNSERVE.EXE service running either (though subversion is installed in
> Program Files\Subversion). Despite this, I can (using TortoiseSVN), create
> a repository on the Y:\ drive and successfully checkout, add, commit and
> update changes to this repository via my repository. The only difference I
> can see is that the repository path is now "file:///Y:/Test Repository" where
> it used to be svn://ACOMPUTER/AFOLDER.
> I can't find anything in the documentation about using SVN in this manner -
> essentially, the only two documented methods I can see is a) APACHE and
> b)SVNSERVE.EXE. I'm mystified as to how the software is actually
> functioning if it's not running as a service on either of the two machines
> that are a) hosting and b) communicating with the repository.
Then you must not be reading any of the Subversion documentation I'm used to
seeing (like the SVN Book). It's in there.
> Am I OK to use Subversion in this fashion? Is there anything I need to be
> aware of?
No. It's dangerous to use the file:// protocol on network shares.
Received on 2008-07-10 18:28:13 CEST