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

RE: recursive find locks/unlock in repository

From: Todd C. Gleason <tgleason_at_impac.com>
Date: Fri, 21 Aug 2009 07:54:28 -0700

________________________________

From: Ullrich.Jans_at_elektrobit.com [mailto:Ullrich.Jans_at_elektrobit.com]
Sent: Friday, August 21, 2009 1:57 AM
To: Gleason, Todd; users_at_subversion.tigris.org
Subject: RE: recursive find locks/unlock in repository

 

Hi everyone,

First thing: sorry for the other post - Out&**% got away from me.

Second: sorry for the top post - Out&*^k won't let me post normally on
this mail - weird, it wants to extend the quote...

Anyway: try this:

svnadmin lslocks <path_to_repo> |grep -B2 Owner |grep Path |sed "s/Path:
\///" |xargs svnadmin rmlocks <path_to_repo>

I suspect this grep for the owner can be left out as well, but I wrote
this some time ago and there were only the locks of a certain user to be
deleted. (In the original, there was another grep -B2 <username> to only
unlock the stuff that user had locked...

Of course, this is supposed to be done on the server.

Cheers, Ulli

Thanks, Ulli. That should speed things up the next time, provided I can
get that set of Unix tools installed on a Windows server (I did find
them all on SourceForge at least). It's unfortunate we have to run it
on the server at all, but I'm sure we can manage that for as rarely as
we'd need to do this.

 

BTW, in Outlook, the trick I use is to hit Ctrl-Shift-C at the top, and
go to where I want to type and hit Ctrl-Shift-V. Applying the style
that way wipes out the extension of quote lines.

 

--Todd

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2386031

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-21 17:00:08 CEST

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.