[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Working copy on a network share

From: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-09-23 12:35:14 CEST

On Sep 23, 2005, at 11:36, Colin JN Breame wrote:

> On Wednesday 21 September 2005 15:23, Leon Zandman wrote:
>
>>> As I understand, it is Not A Good Idea to store the
>>> repository on a network share as their are problems with file
>>> locking.
>>
>> [...] a network share isn't a problem when using FSFS.

> Looks good although I'm having problems when using Berkeley DB
> backend on a
> samba share. It tells me that it cannot move the entries file
> from .svn/tmp
> to .svn. This is because .svn/entries does not have the write
> permission
> set. The message I get is:
>
> svn: Can't move '.svn/tmp/entries' to '.svn/entries': Permission
> denied
>
> I fixed (hacked?) this by adding a call to
> svn_io_set_file_read_write in both
> svn_io_remove_file and svn_io_file_rename. This probably isn't the
> most
> correct way of fixing it but it works for me.

Wait, what? Are you saying that your BerkeleyDB-based repository is
stored on a Samba share? If so, that would be a bad idea; a
BerkeleyDB-based repository should only be stored on a local disk.

I think you're instead saying that your repository is BerkeleyDB-
based, and that it is on a local disk on the server, but that your
working copy is on a Samba share, and that this is not working. If
so, that should be unrelated to the storage engine used for the
repository.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 23 12:36:53 2005

This is an archived mail posted to the Subversion Users mailing list.