Yessir. It's a complete solution and more robust in many other ways.

On Nov 5, 2010, at 6:44 PM, Frank Church <vfclists@gmail.com> wrote:

>
>
> On 6 November 2010 01:33, Michael Shadle <mike503@gmail.com> wrote:
> On Fri, Nov 5, 2010 at 6:15 PM, Frank Church <vfclists@gmail.com> wrote:
>
> > Does that mean that if different users are to run their fastcgi in their
> > home folders with their own user permissions like Apache's suexec a
> > separate fastcgi in /etc/init.d must be created for them?
>
> i have a different port for each user for fastcgi under php-fpm and
> forward from nginx as appropriate. other people do this, or use socket
> files instead of tcp ports.
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx
>
> I take it that php-fpm eliminates the need for spawn-fcgi and php-fastcgi altogether?
>
> --
> Frank Church
>
> =======================
> http://devblog.brahmancreations.com
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx