Thanks for the reply Lee! I'll work on reproducing this sans capistrano - shouldn't be hard if the problem really is in net-ssh. I'll let you know what I find.
One other bit I forgot to include in the original post: the client is Max OSX 10.6.4 (Snow Leopard). Thanks, Mike On Thu, Oct 21, 2010 at 1:06 AM, Lee Hambley <lee.hamb...@gmail.com> wrote: > Mike, > > We'd love some input on this - the only thing we can possibly suggest is to > try a standalone Net::SSH script (since you can reliably reproduce this) and > take Capistrano out of the equation, I don't know of anything in Cap that > would cause this behaviour, but naturally better to isolate it > > If you can do that, and can then give us anymore information (relevant > server SSH logs, (network trace, maybe?), remote ssh server version & info) > - I can pick this up with Delano Mandelbaum who is maintaining Net::SSH - we > have been planning to tackle this as soon as we get a reliable reproduction > case (neither of us have been able to.) > > That's the best I can say Mike, I really wish I could do more - please, > ping me off-list if any of this can't happen in a public forum. > > Sincerely, Lee > > -- > * You received this message because you are subscribed to the Google Groups > "Capistrano" group. > * To post to this group, send email to capistrano@googlegroups.com > * To unsubscribe from this group, send email to > capistrano+unsubscr...@googlegroups.com<capistrano%2bunsubscr...@googlegroups.com>For > more options, visit this group at > http://groups.google.com/group/capistrano?hl=en -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to capistrano@googlegroups.com * To unsubscribe from this group, send email to capistrano+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
