search for: frao_handler

Im trying to get a new app up on dreamhost. What fun :/ Id like to try out the ''frao_handler'' which just keeps dreamhost from automatically killing my fcgi processes. But Im also worried about things getting out of hand. I seem to remember that captures in views can cause problems with fcgi (I might just be making that up????), and I do have few in my app. And well Im just...

...andler.process! nil, 50 # # # Custom log path, normal GC behavior. # RailsFCGIHandler.process! ''/var/log/myapp_fcgi_crash.log'' # require File.dirname(__FILE__) + "/../config/environment" require ''fcgi_handler'' class RailsFCGIHandler private def frao_handler(signal) dispatcher_log :info, "asked to terminate immediately" dispatcher_log :info, "frao handler working its magic!" restart_handler(signal) end alias_method :exit_now_handler, :frao_handler end RailsFCGIHandler.process! -- Posted via http://www.ruby-f...

...production mode on dreamhost I can access the website fine, and everything seems to work. I have a dispatch.fcgi file that reads : #!/usr/bin/ruby require File.dirname(__FILE__) + "/../config/environment" require ''fcgi_handler'' class RailsFCGIHandler private def frao_handler(signal) dispatcher_log :info, "asked to terminate immediately" dispatcher_log :info, "frao handler working its magic!" restart_handler(signal) end alias_method :exit_now_handler, :frao_handler end RailsFCGIHandler.process! and a line in public/.htacces th...

Is anybody getting acceptable performance with a Rails application on Dreamhost? By this, I mean response times no greater than 3 seconds, and no large numbers of FCGI processes that you have to kill manually. If so, how? I''ve ended up running a constant ping script (once every ten minutes), and still have to kill some number of excess dispatch.fcgi processes every day. Along with