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

svn up known issue?

From: jason marshall <jdmarshall_at_gmail.com>
Date: 2005-07-26 20:06:41 CEST

We have a very large code repository that we've been evaluating with
Subversion. It's very sluggish, unacceptably so, but that's not the
particular issue I'd like to address.

What I wish to discuss is that 'svn up' doesn't clean up after itself
if user authentication times out. I have verified this behavior under
1.1.4 and 1.2.1 on Windows XP.

We are retrieving files via svn+ssh, from an FSFS repository on our
LAN. 'svn up' takes a good ten minutes (and 60M of memory) to run
before it finally asks for my password. What it's doing during this
time period, I cannot say, but it's surely not economizing on human
time by doing so. If I should unsurprisingly get bored or step away
from my computer, I may miss this prompt. At this point the clock is
ticking before the connection is lost, and by the time I type in my
password, it may be too late. In this case, I get a "Connection
closed unexpectedly" error, and running 'svn up' again tells me that:

svn: Working copy '.' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)

In which case svn cleanup can take another 20 minutes to run
(consuming 100M of memory), after which I can look forward to another
10 minutes of twiddling before I can run update again.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 26 21:01:39 2005

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

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