how to kill and then cleanup a svn command?

[Joseph Silverman]

I am running "svn commit -m 'bleh'" - this hangs forever with no
indication as to what is wrong. so I do a control-c on it and nothing
happens. so I do a control-z and bg on it and then try "kill %1".
that doesn't work either. When I do kill -9 %1" it dies fine, but then
when I do any svn command, I get "working copy '.' locked". So I do
"svn cleanup" and that hangs forever. What gives?? Seems to me that
svn should ALWAYS be able to die when killed -1 cleanly.
P.s. This svn server is doing nothing at all at the time and the
machine is mostly idle.

[Ben Collins-Sussman]

Post by Joseph Silverman
I am running "svn commit -m 'bleh'" - this hangs forever with no
indication as to what is wrong. so I do a control-c on it and nothing
happens. so I do a control-z and bg on it and then try "kill %1".
that doesn't work either. When I do kill -9 %1" it dies fine, but
then when I do any svn command, I get "working copy '.' locked". So I
do "svn cleanup" and that hangs forever. What gives?? Seems to me
that svn should ALWAYS be able to die when killed -1 cleanly.

The svn commandline client installs a SIGINT handler that sets a flag,
and then constantly checks the flag to see if the user has interrupted.

It works really well, except for a bug in neon. Read about it here:

http://subversion.tigris.org/issues/show_bug.cgi?id=1709

We hear that this bug is fixed in neon's trunk (yes, neon is using svn
now!), and will be released in neon 0.25. We're trying to encourage
neon 0.25 to come soon, so we can couple it with svn 1.2.

[Clemens Schwaighofer]

Post by Joseph Silverman
I am running "svn commit -m 'bleh'" - this hangs forever with no
indication as to what is wrong. so I do a control-c on it and nothing
happens. so I do a control-z and bg on it and then try "kill %1". that
doesn't work either. When I do kill -9 %1" it dies fine, but then when
I do any svn command, I get "working copy '.' locked". So I do "svn
cleanup" and that hangs forever. What gives?? Seems to me that svn
should ALWAYS be able to die when killed -1 cleanly.
P.s. This svn server is doing nothing at all at the time and the machine
is mostly idle.

I had exactly the same, my reason was that a backup got "killed" and I
had to svnadmin recover the repository. Then it worked fine.

Yeah and a hanging svn has to be -9 killed. but as ben said, that will
be fixed in future.

lg, clemens