[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn eats all memory, OOM killer kicks in

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-04-15 19:52:12 CEST

On Mon, Apr 15, 2002 at 11:01:43AM -0500, cmpilato@collab.net wrote:
> So, while your commit succeeded in the repository, your client was
> Killed before the working copy was fully modified to reflect that it
> *knew* your commit had succeeded (thus the reason why some of your
> files were still marked for addition, and some weren't). Well, that's
> just a bogus place to be from a working copy standpoint, as you can
> imagine.

But even if it crashed, it *should* be okay, right? The WC would still show
items to commit, the user would try it, and then get a conflict. An 'update'
would then merge in the changes (already there!) and all would be happy.

The thing is, the client should be able to die (kill -9) at any point, and
thing should work except for a possible need to use 'svn cleanup'.

Maybe we can think of some way to test for killability in the client?


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 15 19:52:41 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.