Re: Command-line option for changing block-on-recover behavior considered unnecessary.

I'd like to make a proposal that incorporates some of the best ideas
from recent posts.

We can't portably determine the other locking processes; attempting to
do so would be too much extra complexity. Plus, some people do run
repositories over very reliable remote filesystems, in which case
lsof/fuser is no help anyway (thanks to ghudson for pointing this out
in IRC). Detecting and auto-killing competing processes, for --force,
would be even harder and more error-prone. "I ran 'svnadmin recover'
and _what_ died??"

But we can make 'svnadmin recover' much friendlier than it is now (and
IMHO, friendly enough) without going into such complexity:

   By default, 'svnadmin recover' fails immediately if it can't get a
   lock, otherwise takes the lock and begins recovering, in
   non-interruptible mode.

   But when passed the '--wait' option, if it can't get the lock, it
   prints out a message saying:

   "Waiting for lock. Currently, at least one other process has the
    repository open; recovery will start when the repository is
    released. Press ^C to give up."

   Then when it gets the lock, it prints out a second message:

   "Lock acquired, starting recovery. This is non-interruptible."

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 30 18:13:38 2004