Hello,
Am 15.08.2012 13:35, schrieb Philip Martin:
There was a bug that caused unlock to leave the files:
http://subversion.tigris.org/issues/show_bug.cgi?id=3667
It is fixed in 1.6.13 but the files will remain until a suitable new
lock/unlock causes them to be deleted.
Thank you for this hint
"rog7...@web.de" writes:
> Hello Daniel,
>
> Am 11.08.2012 00:29, schrieb Daniel Shahaf:
>> If you lock /foo/bar/baz then db/locks/${hash} files are created for each of
>> / ,
>> /foo , /foo/bar .
>>
>> Consequently, if (a) there are no locks in the repository, and (b) no
>> locks are being add
Hello Daniel,
Am 11.08.2012 00:29, schrieb Daniel Shahaf:
If you lock /foo/bar/baz then db/locks/${hash} files are created for each of / ,
/foo , /foo/bar .
Consequently, if (a) there are no locks in the repository, and (b) no
locks are being added or deleted (eg: the server is in read-only mo
rog7...@web.de wrote on Thu, Aug 09, 2012 at 19:18:40 +0200:
> Hello,
>
> I'm wondering about some files in the subfolders of db/locks
> (Subversion 1.6, FSFS). The existence of a lot of files in this
> directory seems to slow down some operations, especially with
> TortoiseSVN. I understand, that
Hello,
I'm wondering about some files in the subfolders of db/locks (Subversion
1.6, FSFS). The existence of a lot of files in this directory seems to
slow down some operations, especially with TortoiseSVN. I understand,
that each locked file in the repository leads to a file (or two?) in
db/
