You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Kieran Kelleher <ki...@mac.com> on 2008/05/18 20:40:17 UTC

Killed by signal 15.

Hello list,

I have various machines accessing a repository using svn+ssh and no  
issues .... up until I gave access to a new user account on dreamhost.

So when I do svn operations I get the 'Killed by signal 15." error  
message. Checkouts and updates seem to work, but in the case of  
updates this error is printed to the console after the update.

For svn checkout, the "Killed by signal 15." is printed to the  
console, followed by the checkout verbose itemized files being checked  
out and then the last console line says "Killed by signal 15." again.

Repository is a file-system type and running svn version 1.4.4.

The client (dreamhost user account) is running svn 1.4.2.

Any ideas what is causing the client to display this "Killed by signal  
15." message?

Regards, Kieran

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

Re: Killed by signal 15.

Posted by Alan Barrett <ap...@cequrux.com>.
On Sun, 18 May 2008, Kieran Kelleher wrote:
> I have various machines accessing a repository using svn+ssh
> So when I do svn operations I get the 'Killed by signal 15." error message. 

svn kills ssh in very nasty ways, whose details have changed from one
version of svn to another.  In my opinion, the fix is as described in
<http://svn.haxx.se/dev/archive-2006-03/0984.shtml>.  I don't know of
anybody working to implement a fix.

--apb (Alan Barrett)

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