Philip Martin wrote:
> Garrett Rooney <rooneg@electricjellyfish.net> writes:
>
>
>>another thing that's popped up is that if i control-c out of a long
>>running update, we end up leaving lockfiles all over the place, even
>>though we errored out with SVN_ERR_CANCELED. if someone who has more
>>clue about how the locking in libsvn_wc works could explain how this
>>can happen, i'd appreciate it. should there be an error condition
>>where we leave the working copy locked?
>
>
> If you interrupt the running of a log file, then the lock on that
> directory cannot be removed. You will need to run 'svn cleanup' to
> rerun the log file and remove the lock. A log file is a file called
> "log" in the .svn directory, if it does not exist then a pool cleanup
> handler should remove the lock.
in that case, should we simply require that the user run 'svn cleanup'
if that happens, or would it be worthwhile to have us check for such a
situation and run cleanup ourselves before exiting after the cancelation?
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 16 19:36:15 2002