So I can launch with a single command line

spawn-fcgi -some -options some-other-cgi-stuff-than-php here

and it will allow more than one concurrent connection?

I think the latest version might have mentioned supporting something, but I'd be looking at leveraging it to manage fcgiwrap, and I don't want to have to launch one spawn-fcgi command for every individual amount of requests I intend.

i.e.

I want a pool of fcgiwrap resources available using a single command line for a specific website. I want to give it a specific user/group ID to run as. (or anything else like fcgiwrap, basically I want to run non-PHP CGI scripts (perl, compiled CGI) from nginx)

It sounds like the latest updates to spawn-fcgi might help this become a reality. Did you say you maintained the project? Have any command line options that I can try to make this happen? I want to be able to support say, 10 concurrent requests. In PHP that would translate roughly to 10 php children (-C 10 I think?)

Do I have to do this 10 times: spawn-fcgi -a -b -c /usr/local/bin/fcgiwrap

Or can I launch it just once with some parameters?

The biggest problem is still that spawn-fcgi is known to crash and hang - separate issue, I know. There are lots of references on it. Consult Professor Google and you'll find many. I'd start with http://www.google.com/search?q=spawn-fcgi+crash and http://www.google.com/search?q=spawn-fcgi+hang. I haven't tried using it in a year or more. Perhaps it's improved in that regard but I'm reluctant to use it in a production environment when php-fpm is just about bullet-proof as it gets. Of course that assumes that development of php-fpm continues as it's presently a one man show AFAIK. Now I'm aware that this doesn't happen on every system but it happens a lot and it has happened to me.

Aside from that, even though fcgiwrap is capable of running several processes simultaneously, spawn-fcgi will only start one. I may be wrong but I believe that's an inherent limitation of spawn-fcgi's command options.