"rog7...@web.de" <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 added or deleted (eg: the server is in read-only mode),
>> then it ought to be safe to remove all those hashes.
>
> Thanks for the explanation. But why do I still see these files
> although all locks in this repository have have been removed some
> weeks ago? Is this intended or a misbehaviour of the subversion
> server?
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.
--
Philip
