Ctrl+C (SIGINT) behaviour for svn command line program

[Alejandro Forero Cuervo <az...@freaks-unidos.net>]

I've found the svn command line program reacts to SIGINT slightly
differently to what I expect from Unix programs.  It seems that when
it receives SIGINT, it starts to close connections and try to
shutdown, which is what I expect.  However, upon receiving further
SIGINT signals, I would expect the process to just terminate, right
away, which it doesn't.

Often times I do:

  svn log | less

Then I read some portions of the log and then just quit less.
However, svn log takes quite a while to close, so I frequently find my
self sending it a SIGTERM to be able to continue to use my shell.

Hence my question: are there any reasons for svn to ignore SIGINT
signals after the first it receives (rather than use the default
handler which just terminates the process)?

Thanks.

Alejo.
http://azul.freaks-unidos.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Ctrl+C (SIGINT) behaviour for svn command line program

[Giovanni Bajo <ra...@develer.com>]

Erik Huelsmann wrote:

>> Hence my question: are there any reasons for svn to ignore SIGINT
>> signals after the first it receives (rather than use the default
>> handler which just terminates the process)?
>>
>> Thanks.
>
> It tries to terminate the process ASAP, but it insists on cleaning up
> behind it in order to make sure your working copy is left in a clean
> state. Extra SIGINT signals don't change that.

Well, surely svn log does not require any cleanup, and so do many other
operations. The behaviour of SIGINTs subsequent to the first one could be
specialized on a case by case scenario.
-- 
Giovanni Bajo



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Ctrl+C (SIGINT) behaviour for svn command line program

[Erik Huelsmann <eh...@gmail.com>]

> Hence my question: are there any reasons for svn to ignore SIGINT
> signals after the first it receives (rather than use the default
> handler which just terminates the process)?
>
> Thanks.

It tries to terminate the process ASAP, but it insists on cleaning up
behind it in order to make sure your working copy is left in a clean
state. Extra SIGINT signals don't change that.

You don't mention which svn version you use nor which access protocol.
I assume you use HTTP? Is it linked against neon 0.25.x? Neon 0.25.x
should have solved some of this behaviour: it has extra functions
(compared to 0.24) for cancelling requests.

HTH,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org