Hello,

I'm using the following ssh configuration:

  ControlMaster auto
  ControlPath ~/.ssh/%r@%h:%p

Unfortunately, it seems that darcs doesn't care if there's already an
existing ControlMaster that it could use: it always creates a new one in
/tmp/darcs-ssh, which will require me typing the password.  I can work
around this by using --disable-ssh-cm, but darcs really should be smart
enough to figure this out by itself.

Currently, darcs runs ssh -O invalid_command to test wether ssh supports
the control feature at all.  Maybe it can instead run 'ssh -O check
<host>' to check wether there is a suitable master process running.

Best regards,
Georg
-- 
Who says nothing is impossible?  I've been doing nothing for years.

On Tue, Jan 09, 2007 at 21:45:08 +0000, Georg Neis wrote:
> Unfortunately, it seems that darcs doesn't care if there's already an
> existing ControlMaster that it could use: it always creates a new one in
> /tmp/darcs-ssh, which will require me typing the password.  I can work
> around this by using --disable-ssh-cm, but darcs really should be smart
> enough to figure this out by itself.

> Currently, darcs runs ssh -O invalid_command to test wether ssh supports
> the control feature at all.  Maybe it can instead run 'ssh -O check
> <host>' to check wether there is a suitable master process running.

This is worth looking into.

As seen in this other issue reports, there are now good alternatives to SSH
controlmaster:

http://bugs.darcs.net/issue437

I suppose this "wish" can remain open if someone wants to improve the
controlmaster feature anyway.

I think we should just consider this obsoleted by the new darcs transfer-mode
(patches welcome!, otherwise)