What''s the deal with fastcgi? Seems like it wants to give my system a little forkbomb every time I start it up. Before today, I had lighttpd configured with just one rails project in fastcgi, and when starting lighttpd up, my load average would peak around 6 (!) before going back down. No pages load while the load average is so high, but they do load quite quickly after it goes back down. Now I''m attempting to add a second rails project to the server, and the load average goes up to 10(!!) and climbing (!!!), showing no signs of letting up. Nothing loads or works properly under this kind of load, it''s a miracle my ssh session is as responsive as it is. I thought this might be because fastcgi is spawning child processes that aren''t loading in time for the idle-timeout, so it''s killing them and restarting them, causing it to constantly start new processes until enough "catch" for it to work properly. So I set the idle timeout to an hour, and it was an improvement, but not a big one. The difference now is that when it climbs up to load average 10, it does so in increments of .2 every 5 seconds instead of incriments of 1. What''s going on? How do I make fastcgi stop forkbombing my system so that I can actually get to using it? -- One Guy With A Camera http://rbpark.ath.cx