I just noticed something odd about "svnadmin lslocks"... perhaps a bug?
The (short version) backstory is that I am trying to clear all locks
from a repository (they are all stale) with something like "svnadmin
lslocks repos | xargs svnadmin rmlocks repos" (the exact script is more
complicated, but you get the idea). That seemed to work, but I still
got errors due to the locks.
The svnadmin lslocks command listed no locks, but if I specified the
pathname from the error message I get, the lock is, indeed, present:
$ svnadmin lslocks /scm/svn/repos/hhhh
$ svnadmin lslocks /scm/svn/repos/hhhh '/some/file/omitted.foo'
Path: /some/file/omitted.foo
UUID Token: opaquelocktoken:52effd7a-fadc-11e9-9fa4-db671f4521f1
Owner: somebody
Created: 2019-10-30 06:13:00 +0000 (Wed, 30 Oct 2019)
Expires:
Comment (1 line):
something
This seems like a bug in lslocks, why would it not list *all* the locks?
Or am I doing something wrong?
This is SVN 1.10.4 on Linux
++thanks,
trent...
