I have never used fcgiwrap and in fact just discovered it. As I understand it, it uses fcgi to then spawn cgi processes? Why not code the application as a FastCGI one? That would be way faster in terms of performance. The only reason you would need that is to either run CGI apps on a remote host or to overcome the lack of cgi support in nginx.

And all you find via google are invalid bugreports. Saying something can be found on the internet doesn't make it true. Again I think you guys completely misunderstand the role of spawn-fcgi. It sets up some sockets and spawns a processes. That's basically it. It is in NO way involved with handling the requests. If something crashes or hangs then that's the fault of the application. PHP in this case (and it has been known to do so in past releases). This is not spawn-fcgi's fault. After spawning the application, spawn-fcgi is no more around normally. How can something that is not running cause such problems?

You can of course (as I said earlier) start multiple processes by calling spawn-fcgi multiple times (with different command options for the address).

Telling spawn-fcgi to spawn like 10 processes is not possible because how should it know which addresses to bind to?