jim.ohlstein at gmail.com
Fri Feb 27 02:10:59 MSK 2009
Unless it has changed in the latest version (I haven't looked at the documentation), spawn-fcgi's "-c" option only applies to php-cgi processes. I tried it with fcgiwrap and got only one instance. Using the script that Grzegorz wrote you can generate as many as you like, and they are cheap memory-wise.
Sent from my Verizon Wireless BlackBerry
From: mike <mike503 at gmail.com>
Date: Thu, 26 Feb 2009 14:20:18
To: <nginx at sysoev.ru>
Subject: Re: FCGI.pm ?
oh, dur. I would need one
spawn-fcgi fcgiwrap etc ...
for -every- "child" instance available. since it only does PHP
children itself, yeah?
On Thu, Feb 26, 2009 at 11:53 AM, Jim Ohlstein <jim.ohlstein at gmail.com> wrote:
> But only for one instance of fcgiwrap Mike. If you want multiple instances the script works perfectly.
> ------Original Message------
> From: mike
> Sender: owner-nginx at sysoev.ru
> To: nginx at sysoev.ru
> ReplyTo: nginx at sysoev.ru
> Subject: Re: FCGI.pm ?
> Sent: Feb 26, 2009 12:48 PM
> On Thu, Feb 26, 2009 at 4:03 AM, Grzegorz Nosek
> <grzegorz.nosek at gmail.com> wrote:
>> Yup. Providing the socket for fcgiwrap to listen on is your problem
>> (fcgiwrap doesn't care whether it is a tcp socket or a unix domain one
>> etc.). The simplest way to run a single fcgiwrap is to use spawn-fcgi,
>> like this:
>> spawn-fcgi -f /usr/local/bin/fcgiwrap -a 127.0.0.1 -p 8001
>> spawn-fcgi -f /usr/local/bin/fcgiwrap -S /tmp/cgi.sock
> Oh? spawn-fcgi will work too? Not the perl-based example? Cool. That
> made life a little bit easier for me as I have scripts and things that
> I had made to control spawn-fcgi stuff.
> I'm still excited for a php-fpm style management daemon though :)
> I will need to try spawn-fcgi + fcgiwrap soon!
> Sent from my Verizon Wireless BlackBerry
More information about the nginx