On 7/19/05, Paul Wistrand <me / paulwistrand.com> wrote:
> Has anyone been successful in getting this combination (Rails, Lighttpd,
> FastCGI and Cygwin) working? I'm at my wits end trying to get rails working
> on anything other than webbrick which
> is just too slow to even get learning on. Please any help will be very
> appreciated.
> 
> Currently my fcgi crash log throws out this
> [19/Jul/2005:15:20:24 :: 888] Dispatcher failed to catch:  (Interrupt)
>   /usr/lib/ruby/gems/1.8/gems/fcgi-0.8.6.1/./fcgi.rb:597:in `each'
>   /usr/lib/ruby/gems/1.8/gems/fcgi-0.8.6.1/./fcgi.rb:597:in `each_cgi'
>   /usr/lib/ruby/gems/1.8/gems/rails-0.13.1/lib/fcgi_handler.rb:55:in
> `process!'
>   /usr/lib/ruby/gems/1.8/gems/rails-0.13.1/lib/fcgi_handler.rb:21:in
> `process!'
>   /home/Administrator/projects/rails/Todo/public/dispatch.fcgi:24
> killed by this error
> 
> And my server log this
> 2005-07-19 14:50:45: (log.c.67) server started
> 2005-07-19 14:51:48: (mod_fastcgi.c.1466) connect delayed, will continue
> later: 7
> 2005-07-19 14:51:48: (mod_fastcgi.c.2487) got proc: 7 0
> /tmp/application.fcgi.socket-2 0 1
> 2005-07-19 14:51:48: (mod_fastcgi.c.2558) write failed: Broken pipe 32
> 2005-07-19 14:51:48: (mod_fastcgi.c.2613) fcgi-server disabled:  0
> /tmp/application.fcgi.socket-2
> 2005-07-19 14:51:48: (mod_fastcgi.c.1287) release proc: 7 0
> /tmp/application.fcgi.socket-2
> 
> 
> 
> 
> 

I don't think many people use Cygwin here, since there isn't much
reason to, and it's not native.

I'm suprised you found webbrick slow for learning. How are you running
it, and on what kind of machine?

Regards,
Nick
-- 
Nicholas Van Weerdenburg