I'm running 1.8.6. I have the 'fastthread' 1.0 gem for mongrel. When I did a require for that at the top of my Capfile or my config/deploy.rb, I still had the client side go into 100% cpu. I have no problem doing a cap shell to that machine. Also, I don't think it is a gateway issue. I tried it both ways.
I'm definitely thinking this is a threading issue on the cap command line side. Is there a way to force this into a single threaded mode? On 7/10/07, Ezra Zygmuntowicz <[EMAIL PROTECTED]> wrote: > > > > What version of RUby itself are all of you experiencing this > problem > running? Is it perhaps ruby 1.8.6? I've been doing file transfers > with cap here of up to 25Mb without ever seeing this issue no matter > what i call before or after the put command. THis was with ruby 1.8.5 > > But I just tried it with ruby 1.8.6 and was able to get the same > deadlocking error. Ruby 1.8.6 has a bug in the threading code that > causes deadlocks sometimes. > > Can those of you having this issue please install the fastthread > gem > and add require 'fastthread' to the top of your recipe files and > report back please? > > Thanks > -- Ezra Zygmuntowicz > -- Lead Rails Evangelist > -- [EMAIL PROTECTED] > -- Engine Yard, Serious Rails Hosting > -- (866) 518-YARD (9273) > > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
