Re: [us...@httpd] Re: recommended setup apache/php

2010-07-27 Thread Nilesh Govindarajan
On Tue, Jul 27, 2010 at 7:58 PM, Hajo Locke wrote: >>> On 2010-07-27 10:15, Nilesh Govindarajan wrote: > > If I understood your question properly, you're asking that > /htdocs/a.php is one fastcgi app and /htdocs/b.php is another. > If you want it this way, then you will have to ad

[us...@httpd] Re: recommended setup apache/php

2010-07-27 Thread Hajo Locke
On 2010-07-27 10:15, Nilesh Govindarajan wrote: If I understood your question properly, you're asking that /htdocs/a.php is one fastcgi app and /htdocs/b.php is another. If you want it this way, then you will have to add the shebang (#!) line to all of your scripts before # This config below ensu

Re: [us...@httpd] Re: recommended setup apache/php

2010-07-27 Thread Jonas Eckerman
On 2010-07-27 11:43, Hajo Locke wrote: > there is one sentences in the docs which sounds strange In what way does it seem strange? > Currently, only one FastCGI application of any type (AAA or handler) can > be used for a particular request URI. [...] > this means that only on fcgid-script per

Re: [us...@httpd] Re: recommended setup apache/php

2010-07-27 Thread Nilesh Govindarajan
On Tue, Jul 27, 2010 at 5:26 PM, Jefferson Ogata wrote: > On 2010-07-27 10:15, Nilesh Govindarajan wrote: >> If I understood your question properly, you're asking that >> /htdocs/a.php is one fastcgi app and /htdocs/b.php is another. >> If you want it this way, then you will have to add the sheban

Re: [us...@httpd] Re: recommended setup apache/php

2010-07-27 Thread Jefferson Ogata
On 2010-07-27 10:15, Nilesh Govindarajan wrote: > If I understood your question properly, you're asking that > /htdocs/a.php is one fastcgi app and /htdocs/b.php is another. > If you want it this way, then you will have to add the shebang (#!) > line to all of your scripts before solution if you h

Re: [us...@httpd] Re: recommended setup apache/php

2010-07-27 Thread Nilesh Govindarajan
If I understood your question properly, you're asking that /htdocs/a.php is one fastcgi app and /htdocs/b.php is another. If you want it this way, then you will have to add the shebang (#!) line to all of your scripts before Options +ExecCGI ExpiresActive Off And the source code

[us...@httpd] Re: recommended setup apache/php

2010-07-27 Thread Hajo Locke
PHP in CGI mode consumes lot of memory because, for every request a PHP interpreter is called up, so your memory is filled with N php interpreters executing the same PHP code where N is the number of online users. There is no way to avoid it except using some different method like fastcgi/mod_php.