> > I guess the next thing to do is to try and keep the repository on my
> > windows machine and make backups to the NAS, but I'm not keen on this.
I'm
> > going research git over the next couple of days, and if the problem
> > persists, see if it's worth switching.
> I think when you move from the NAS to keeping the repository on the
> Windows box, you'll see the problem disappear. Accessing repositories
> over shares is known to be a problem due to how locking and other
> mechanisms operate on some network filesharing protocols (and even
> certain versions of those protocols, or certain configurations of
> them).
>
> The advice generally is "don't do that" - it's not really a supported
> configuration. Keep your repository local to the server process
> itself.
The problem first began when the svnserve -d was running on the NAS itself,
where it was accessing local storage. Pulling the server over to the Windows
box hasn't made a difference. While I understand what you're saying, and I'm
going to pull everything over to Windows next, the problem arose before I
made that change.
Phil.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2415639
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-11-09 01:43:10 CET