-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSHKit needs to re-use connections where possible #69
Comments
Pulled down the
like you would expect. |
I love what Mina was trying to do by queueing commands into a single connection. Not suggesting anyone rewrite the Capistrano command backend, mind you. 😸 But it seems better to pool the (costly) connection as much as possible. |
I suggested trying the following to the last person that ran into this: http://www.cyberciti.biz/faq/linux-unix-reuse-openssh-connection/ I'm not sure if Net::SSH is smart enough to do that, but it seems sane to me. Maybe that's a way to keep this pooling out of SSHKit, and push it down to the layer where I think it belongs. (I'm not totally surprised that my branch doesn't work, I don't even know if the memoisation is working. |
In combination with a |
Inneresting! I am on the go now, but will definitely check that out soon.
|
Net::SSH doesn't pick that up, regular |
Thanks for checking Net::SSH, maybe @delano has some idea of of we could Sent from my Nexus 4.
|
I think this can be closed now. /cc @leehambley |
See capistrano/documentation#57 (comment) for original thread
The text was updated successfully, but these errors were encountered: