I'm not sure if the problem I have is something that can be fixed on the fastcgi end of things, but thought I would post to see if anyone else had come across the same issue...
When I set the log_level to :none in my rails app's config, It will not start when running through fastcgi. The rails app will still start from command line Ruby, and will also start using the Mongrel web service gem for Ruby. It only fails when calling it through FastCGI.
If I set the logging to anything other than ":none" (like :info), then everything works just fine.
Sadly, under windows, Ruby only writes one log file, and never releases the lock on that file until you kill the app... Makes disk space a wee bit of an issue when the site needs to be up 24/7 :-)
Any pointers in the right direction greatly appreciated as always. - especially as this may not be something that can be fixed in the fastcgi component!
S.