Thanks for all the data, that's great stuff. I'm still at a loss as to
what the difference is... especially if it works in cap1 but not cap2,
against the same Net::SSH version. If it isn't too much to ask, could
you try comparing the sftp dumps against a cap1 session, to see if
there is any difference?

cap2 did refactor the upload code, but I can't see anything in the
changes that would be significant here...and I *still* can't duplicate
this specific problem. :(

- Jamis

On 7/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> More data. Everytime I run this we get into a 100% cpu situation with cap
> deploy.
> I tried the live debugging in the ruby process and the backtrace(-1) just
> segfaults.
> I tried the ruby debugger and CTRL-C won't interrupt the process.
>
> No joy.
>
> For now, I'm going to stop and work on an older cap 1.x script that I have
> that works.
>
>
>  >
>

--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---

Reply via email to