Can't kill svn

2012-06-01 Thread Andreas Krey
Hi everybody, is there already a bug on this? I can't always get the svn client to stop using ^C. Mostly this seems to happen with slow network I/O, like, for reproduction: prompt> time svn checkout http://217.140.74.17/doesnotexist ^C^C^Csvn: OPTIONS of 'http://217.140.74.17/doesnotexist': c

Re: Can't kill svn

2012-06-01 Thread Michael P. Reilly
On Fri, Jun 1, 2012 at 3:13 PM, Andreas Krey wrote: > Hi everybody, > > is there already a bug on this? I can't always get the svn client to > stop using ^C. Mostly this seems to happen with slow network I/O, like, > for reproduction: > > prompt> time svn checkout http://217.140.74.17/doesnotexi

Re: Can't kill svn

2012-06-02 Thread Stefan Sperling
On Fri, Jun 01, 2012 at 06:19:58PM -0400, Michael P. Reilly wrote: > On Fri, Jun 1, 2012 at 3:13 PM, Andreas Krey wrote: > > > Hi everybody, > > > > is there already a bug on this? I can't always get the svn client to > > stop using ^C. Mostly this seems to happen with slow network I/O, like, > >

Re: Can't kill svn

2012-06-02 Thread Andreas Krey
On Sat, 02 Jun 2012 11:14:16 +, Stefan Sperling wrote: ... > Some signals never have an immediate effect in Subversion. > Subversion handles signals gracefully at defined points to ensure state > is cleaned up properly. Hanging more than a minute isn't exactly what I consider 'graceful'. > Wh

Re: Can't kill svn

2012-06-02 Thread Stefan Sperling
On Sat, Jun 02, 2012 at 10:01:42PM +0200, Andreas Krey wrote: > On Sat, 02 Jun 2012 11:14:16 +, Stefan Sperling wrote: > ... > > Some signals never have an immediate effect in Subversion. > > Subversion handles signals gracefully at defined points to ensure state > > is cleaned up properly. >

Re: Can't kill svn

2012-06-02 Thread Andreas Krey
On Fri, 01 Jun 2012 18:19:58 +, Michael P. Reilly wrote: ... > What release of Subversion and what is your operating system? 1.6.6 and 1.7.4, behaving essentially similar. MacOS 10.5.8. > Standard > network has a timeout of about 120 seconds, but depending on the OS, the > command may not be