svn+ssh breaks with ControlSocket

It would seem that svn brutally kills the ssh process it starts, so
that ssh client can't remove it's ControlSocket. The dangling
controlsocket fools following ssh connections to believe they should
use multiplexed sessions, and fails when they can't use the
controlsocket.

  [21:44] svn ls svn+ssh://venerable/mnt/data/svnroot/plonesvnview
  Enter passphrase for key '/home/quest/.ssh/id_rsa':
  Control socket connect(/tmp/ctl_quest@windwards.net): Connection refused
  Enter passphrase for key '/home/quest/.ssh/id_rsa':

This would seem to be a misfeature in ssh, but svn really shouldn't be
so harsh to its spawned ssh client. Hence I feel this is a bug in svn
and am looking for agreement. What say you?

-- 
"Making digital data less copyable is like making water less wet."
  -- Cory Doctorow
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org