On 2006-12-20 10:34:43 -0700, Alvaro Lopez Ortega <[EMAIL PROTECTED]> said:
> Brian Rosner wrote, On 20/12/06 17:27:
>
> >> Extension php {
> >> Handler fcgi {
> >> Server localhost:8002 {
> >> Env PHP_FCGI_MAX_REQUEST "-1"
> >> Env PHP_FCGI_CHILDREN "5"
> >> #Interpreter "c:\Internet\PHP5\php-cgi.exe -b 8002"
> >> #Interpreter "c:\Internet\cygPHP5\php-cgi.exe -b 8002"
> >> }
> >> }
> >> }
> >
> > FastCGI support in Cherokee on Windows does not currently work
> > properly. Cherokee attempts to run the Interpreter through /bin/sh
> > which will fail on Windows. I am going to look into how to make it
> > work if you use the cgi-fcgi.exe.
>
> As a work around, you could launch the PHP fastcgi server by hand.
> Once it's running Cherokee will be able to relay the PHP requests on
> it.
>
> > I wouldnt expect full Windows support of fastcgi until 0.7.
>
> Why? The fcgi is already included in 0.5, so this is a bug we ought
> to fix in the next minor release (0.5.7).
Maybe this is my misunderstanding of how this works, but does Cherokee
have a fastcgi server that it spawns to handle connections to each PHP
process? So a web request comes in for /test.php then Cherokee checks
if a fastcgi server is running based on the config values, if not it
spawns its own and handles the load balancing and what not.
>From what I saw in the Cherokee source is that when a fastcgi server is
not running it spawns a /bin/sh <interpreter> which fails on Windows.
Based on his configuration above PHP will spawn the 5 children not
Cherokee unless Cherokee handled the fastcgi server.
--
Brian Rosner
http://www.brosner.com/blog
_______________________________________________
Cherokee mailing list
[email protected]
http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
