> From: Jack Repenning [mailto:jrepenning@collab.net]
> Sent: Monday, August 04, 2003 8:12 PM
> (Moved from users to dev)
>
> At 7:56 PM -0400 8/3/03, Garrett Rooney wrote:
> >It's not a simple problem, because svnadmin recover needs to be able
> >to handle the case where the client has crashed while holding the
> >lock, so at least some of the time it needs to forcefully break the
> >lock. This is a bad thing (tm) if the other process actually is
> >still running. The current code doesn't handle this especially well
> >(it just breaks the lock all the time, rather than trying to acquire
> >it normally), so we should definately be doing something else, the
> >question is what?
>
> The danger of corrupting a repo during "recovery" is a really huge
> gotcha! Do we have an issue open to cover this? I can't spot one.
I updated the FAQ. That should help a bit.
What we really need is a mandatory --force flag to svnadmin recover
and a "WARNING: ... Are you sure [yes/no]?" when --force isn't passed.
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 4 20:40:03 2003