Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

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

Killed by signal 15.

during a svn up.

Any ideas way?

share|improve this question
    
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/… –  Zoredache Mar 9 '10 at 20:58
add comment

4 Answers 4

up vote 7 down vote accepted

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: ssh = $SVN_SSH ssh -q

share|improve this answer
    
To make the solution work, you should put the line into [tunnels] section –  xtreye Jul 1 at 3:19
add comment

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.

share|improve this answer
add comment
 ~/.subversion/config: ssh = $SVN_SSH ssh -q

This doesn't work - I think this is the fix for the previous bug.

[n@g ~]$ svn up /opt/
At revision 1492.
Killed by signal 15.
[n@g ~]$ grep "ssh =" ~/.subversion/config
ssh = $SVN_SSH ssh -q
share|improve this answer
add comment

If it isnt working perhaps you are invoking ssh using something other than the $SVN_SSH variable. http://www.freebsdonline.com/content/view/764/528/ has an example of that.

regarding the warning:

"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."

that is because you placed the -q after the -o which is looking for the option (ControlMaster=no) specified by -o. if you placed the -q after the option, it will work. ie

ssh = $SVN_SSH ssh -o ControlMaster=no -q
share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.