Gerry,

Sounds like you want to make use of the upstream module (
http://wiki.nginx.org/NginxHttpUpstreamModule ); something like this
should work:

upstream supercpp {
server backend1.example.com weight=5;
server 127.0.0.1:8080 max_fails=3 fail_timeout=30s;
server unix:/tmp/backend3;
}

Substituing of course your backends and weight settings (if
necessary). Minimal for you might be like:

upstream supercpp {
server unix:/tmp/back0;
server unix:/tmp/back1;
...
}

Then later, when you need to pass off to it, you simply refer to the
upstream group by name like so:

fastcgi_pass supercpp;

Thanks,
Merlin

On 7/21/09, gerryw <nginx-forum@nginx.us> wrote:
> Hello All,
>
> I have finally figured out what the problem was. For some reason when the
> local unix: socket was created there was an OS issue that was corrupting the
> data that nginx was writing to the socket. The problem was solved by
> specifyng an alternate location for the file. I am very happy to find that
> this was not an nginx issue, because I really wanted to use it.
>
> I do have one other question though. I'm trying to find some docs that talk
> about multiple fcgi application instances and how nginx balances requests
> between them. Does anyone know where I could find some info on this?
>
> BTW: My fcgi application is written in C++ using the fcgi library. I am also
> making use of the upload module.
>
> Thanks,
> Gerry
>
> Posted at Nginx Forum: http://forum.nginx.org/read.php?2,4091,4297#msg-4297
>
>
>