Re: apache 2.x and mod_fcgi-- revived?
steve <[email protected]>
| Newsgroups | gmane.comp.web.fastcgi.devel |
|---|---|
| Message-ID | <[email protected]> |
I've seen this (rarely) with static fgci and non-graceful restarts/shutdowns. Only rarely though. Also, I use PHP which has its own process handling, so the advice I was given was to have the fcgi module have one static connection to create a PHP fcgi server (which then sets up a static number if its own). I'm using worker MPM in Apache and would like it to instead have each MPM create its own single PHP fastcgi instance. That way I can tune the number of PHP instances to the number of threads in each Worker (1:15 ratio, for example). When another worker is needed, then another PHP would spawn. It would be great if this worked for the even MPM also. -steve-- On 12/29/05, Justin Dossey <[email protected]> wrote: > In case yall haven't seen, Brian McCallister has started collating a list > of issues with mod_fcgi in apache 2.x. He's listening, so post em up! > > http://kasparov.skife.org/blog/src/apache_22_fcgi.html > > I'll start: > > mod_fcgi doesn't work (well) with the worker mpm. A graceful to apache > will orphan all the fcgi procs and on my systems, the orphans proceed to > eat CPU and bring the system to a grinding halt. At the same time the > orphans are going mad, Apache is blissfully spawning new fcgi procs. > > -- > Justin Dossey > Operations, podOmatic > (415) 975-9981 > > > ___________________________________ > fastcgi-developers mailing list > http://fastcgi.com/fastcgi-developers/ > > > ___________________________________ fastcgi-developers mailing list http://fastcgi.com/fastcgi-developers/