{ 7 comments… read them below or add one }

1 Robert de Bock August 21, 2008

Wow, that is indeed a good trick! Never heard of these configuration variables.

Works on Mac OS X 10.5.4, the only remark;
- I have the options set for no host, so your ~/.ssh/config could just be like this:

ControlMaster auto
ControlPath /tmp/ssh-%r@%h:%p

- The manpage suggests to use the variables with different capitalization. See example above.

Regards and thanks for the great trick, indeed fast!

Robert de Bock.

Reply

2 hilbert00 November 11, 2008

I’m concerned about security. Is there any security issue using re-using ssh connections?

thanks

Reply

3 hypatia February 3, 2009

The ONLY draw back I’ve found to this is that because all subsequent SSH requests to the same host share the TCP connection, doing a bulk SCP will slow down the responsiveness of the interactive sessions. It’s not a problem most of the time.

Reply

4 silvere March 15, 2009

why doesn’t it works in my cygwin?

The error is:
$ ssh sunjingwei@relay01
ssh_msg_recv: read: header
muxclient: msg_recv

thank u very much.

Reply

5 Tamas Herman April 17, 2009

$ ssh -fNM eta
$ ssh eta ls
mm_receive_fd: no message header
muxserver_accept_control: failed to receive fd 0 from slave
ssh_msg_recv: read: header
muxclient: msg_recv

Reply

6 Dale Schaafsma September 2, 2009

FYI, ssh manpages recommend storing the socket in a private location to prevent other users from using the same socket.
As for the cygwin error, my research so far indicates that this is due to passing around a file descriptor… https://bugzilla.mindrot.org/show_bug.cgi?id=1278

Reply

7 Allayna April 16, 2011

You’re the grteesat! JMHO

Reply

Leave a Comment

You can use these HTML tags and attributes for your code and commands: <strong> <em> <ol> <li> <u> <ul> <blockquote> <pre> <a href="" title="">




Previous post:

Next post: