Comment 8 for bug 495000

2009/12/16 John A Meinel <email address hidden>:
> b) Try a short sleep and try-again. This won't fix all cases, and
> eventually we should time out and stop trying. Actually, we probably
> want to move on to renaming all the other files we can, and then come
> back to trying to rename this one. That way the other process doesn't
> hold open another pack file, and in fact, will probably trigger it to
> stop what it is doing completely, freeing up this one.
>
> We could do one loop, or 2, or 5, or X and then stop. I don't think we
> want to try indefinitely.
>
> It certainly can be identified after the fact that this is an
> unreferenced file, though currently we don't have that action
> specifically exposed.

I'd probably try that first, and also make it give a warning that it's
doing so, so that

1- people know why it's slowed down
2- it will come up in later bug reports, if there are any

--
Martin <http://launchpad.net/~mbp/>