On Tuesday, November 01, 2011 1:12 PM, "Neil Bird" <n...@jibbyjobby.co.uk> wrote: > Around about 01/11/11 12:12, Daniel Shahaf typed ... > > "database is locked" is the error SQLite would give when it tries to write > > to a database (.svn/wc.db) on which some other process already has a > > write-lock. The SQLite documentation: > > ... SQLite relies on POSIX advisory locks. Do those locks (fcntl() locks, > > if I read the source correctly) work correctly in your environment? > > No, these are not working (are they even supported by Windows? they seem > to be refs. to Samba server impls). > > I can get it working by mounting my CIFS shares '-o nobrl', which despite > the scary description (about it being unsafe) would seem to be the correct > thing to do in my case. > > I don't do svn ops. on the same repo. in parallel (from both machines at > the same time) anyway. >
The issues are the same for FSFS-backed repositories and for 1.7+ working copies, since both of them use SQLite. (In 1.7 FSFS the sqlite db's are non-authoritative.) However you mentioned CIFS-mounted working copies, in which case the issue will be concurrent access not to the repository but to the working copy. > > I wonder what Windows client sqlite code does over Windows shares (as > that works)? > > -- > [neil@fnx ~]# rm -f .signature > [neil@fnx ~]# ls -l .signature > ls: .signature: No such file or directory > [neil@fnx ~]# exit >
