[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svnadmin lslocks ambiguity

From: Trent Fisher <trent.fisher_at_oracle.com>
Date: Mon, 6 Jan 2020 13:22:24 -0500

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)
Comment (1 line):

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


Received on 2020-01-06 19:22:34 CET

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.