On Oct 8, 2008, at 06:41, Dr. Folkert Janssen wrote:
> I understand that FSFS has to be used when a network share is intended
> to hold a repository accessed with svnserver. A large number of
> contributions on the net indicate that this setup is used quite
> frequently.
> My question now is if the standard MS Windows network share is
> reliable
> enough for hosting a repository keeping its many quirks in mind. Is
> FSFS
> capable of reporting a commit reliably under these circumstances?
I must ask why you want to do this.
If the goal is to have a Windows file server host the repository, and
have multiple users commit to it using file:/// URLs to that file
server, then I must instead recommend you set up svnserve on the
Windows server instead and access the repository through svnserve's
svn:// protocol. In Subversion the file:/// protocol is not designed
for serious multiuser use; it's meant for testing only.
If the goal is to have one server serve the repository via svnserve
while it's physically housed on another server's disk, why add this
complexity? Just host the repository on the server that has the
sufficient disk space. This will be faster and will eliminate any
potential problems you may encounter due to network shares.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-09 01:31:12 CEST