Re: Can't diff after killing svnlook

Greg Ward wrote:

>I presume I have to run "svnadmin recover" on the server. This is more
>than a bit worrying though: for starters, why does svnlook need
>read-write access to the repository? Why does it hose the repository if
>I just kill it with Ctrl-C? That seems rather flaky.`
>

it needs read-write access because it's directly accessing the berkeley
db filesystem, which involves writing to tables for creating locks and
things like that. it's just the way berkeley db works.

the need for some way to support cancelation of long running svn
commands is a well known issue, and it will be fixed at some point (we
know how to do it, it's just a 'small matter of programming'), but for
now, if you kill a process that's accessing the repository directly, you
risk leaving locks around and generally making the filesystem unhappy
(which can be corrected with svnadmin recover).

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 17 20:48:01 2003