On Mon, Apr 13, 2009 at 05:00:57PM +0200, Bernd Zeimetz wrote:
> Philipp Kern wrote:
> > I also found svn to be not Ctrl-C-able at time. I don't know if that
> > applies
> > to other signals too but if so I can imagine quite some hanging processes
> > on a server.
>
> Ack - I know this problem too well. the 'kill -9' axe is the only way to get
> rid
> of svn processes in time, unfortunately.
All you did was preventing SVN from releasing locks. As a long-time user, I
have yet to see an apparent lockup due to something else. SVN uses a
brain-dead way of locking that takes age to clean up, but leaving them stale
is asking for trouble. With that in mind, SVN's decision to always clean up
after a Ctrl-C rather than exit immediately is a sound one.
On the other hand, indeed, taking several minutes to abort an operation on a
project with 64k dirs 250k files in trunk is bad. That's why most of us
have migrated to git.
--
1KB // Microsoft corollary to Hanlon's razor:
// Never attribute to stupidity what can be
// adequately explained by malice.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
