I get Killed by signal 15. when I'm using svn

Question

I'm using svn+ssh and I see a number of:

Killed by signal 15.

during a svn up.

Any ideas way?

Solution 1

The message you are seeing is printed by ssh as a result of the fix for svn-issue #2580.

This is expected. You need to add -q to the ssh command invoked by svn, which happens by default as of 1.6.6.

Put this in ~/.subversion/config under the [tunnels] section:

ssh = $SVN_SSH ssh -q

Solution 2

The correct answer is:

Add the -q parameter after  "$SVN_SSH ssh" in ~/.subversion/config

In plain English:

If your ~/.subversion/config already has such a line, then edit the line. Else add it.

So, if you are sure there is no occurrence of ssh = $SVN_SSH ssh then add a new line:

ssh = $SVN_SSH ssh -q 

If the line already exists, typically as ssh = $SVN_SSH ssh -o ControlMaster=no then edit it to read ssh = $SVN_SSH ssh -q -o ControlMaster=no

Warning: The order of the parameters seems to matter. ssh = $SVN_SSH ssh -q -o ControlMaster=no works, but ssh = $SVN_SSH ssh -o -q ControlMaster=no fails with the message command-line: line 0: Bad configuration option: -q.

Comments

[Zoredache]

There are a large number of hits for google.com/search?q=svn+signal+15 looking through them there does seem to be a known bug for older versions of subversion that require you to update your .subversion/config old.nabble.com/…

[no id]

To make the solution work, you should put the line into [tunnels] section

[Allan Jude]

The order matters because 'ControlMaster=no' is a parameter of -o. -o is not a stand-alone flag

[javabrett]

Note that the fix applied to Subversion somewhere from about 1.6.5 onwards is only to the default ssh setting in your config [tunnels] section. If you have an existing installation with that set, e.g. ssh = $SVN_SSH ssh -o ControlMaster=no, (sans -q) then you will need to add that setting there, as the updated default will not apply.