Trent Fisher wrote on Wed, Jan 15, 2020 at 15:00:56 -0500:
> On 1/6/2020 1:42 PM, Daniel Shahaf wrote:
> > Trent Fisher wrote on Mon, 06 Jan 2020 18:22 +00:00:
> > > This seems like a bug in lslocks, why would it not list *all* the locks?
> > If you run fsfs, it might be
> > https://urldefense.pro
On 1/6/2020 1:42 PM, Daniel Shahaf wrote:
Trent Fisher wrote on Mon, 06 Jan 2020 18:22 +00:00:
This seems like a bug in lslocks, why would it not list *all* the locks?
If you run fsfs, it might be
https://urldefense.proofpoint.com/v2/url?u=https-3A__subversion.apache.org_issue3750&d=DwIBAg&c=R
Trent Fisher wrote on Mon, 06 Jan 2020 18:22 +00:00:
> This seems like a bug in lslocks, why would it not list *all* the locks?
If you run fsfs, it might be https://subversion.apache.org/issue3750.
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,
