[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: Colin JN Breame <colin_at_breame.net>
Date: 2005-09-23 11:36:37 CEST

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.

I might look into converting bdb to fsfs as a more permanent solution.


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.
> From the TortoiseSVN documentation:
> "The FSFS format is faster (than Berkeley DB) and it now works on
> network shares and Windows 98 without problems."
> So a network share isn't a problem when using FSFS.
> Greetings,
> Leon Zandman

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 23 11:38:43 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.