nstead of calling the binary directly
(e.g. for virtual hosting environment), and risk users getting rid of
the wrapper scripts by accident.
Regards,
Filip Hajny
-
This SF.net email is sponsored by: Splunk Inc.
Still gre
Is there a known way how to pass PATH_INFO to PHP on mod_fcgid? I
have tried both using FCGIWrapper and AddHandler approaches, but PHP
ends up with an empty environment (other than what's raised using
DefaultInitEnv or in the shell wrapper script - like PHPRC). The way
I see it, this is act
On 13.9.2007, at 8:08, Joachim Durchholz wrote:
> Filip Hajny schrieb:
>> Is there a known way how to pass PATH_INFO to PHP on mod_fcgid? I
>> have tried both using FCGIWrapper and AddHandler approaches, but PHP
>> ends up with an empty environment (other tha
On 13.9.2007, at 10:14, Joachim Durchholz wrote:
> Could you provide us a URL that gives us phpinfo output? We could then
> take a closer look; it's a bit difficult to discern what's going wrong
> with the information that we have.
> Preferrably two URLs, one for a mod_php and one for a mod_fcgid s
Now I feel like a true idiot. I believed that PATH_INFO will always
be populated, instead it's only populated if there is any, well, path
info provided.
> http://phptest.joyeurs.com/cgi/index.php/wrzlbrmft
> http://phptest.joyeurs.com/fcgi-action/index.php/wrzlbrmft
> http://phptest.joyeurs.co
I suggest you do away with PHP's own spawning (remove all mentions of
PHP_FCGI_CHILDREN) and let mod_fcgid do the job on its own. That way
at least, it's dynamic, well controllable
(DefaultMinClassProcessCount, DefaultMaxClassProcessCount), and you're
not multiplying process counts by runni
t know anything about
this, so you're essentially spawning processes at two levels
(mod_fcgid and PHP itself). My suggestion is to yank our
PHP_FCGI_CHILDREN completely. Just leave the process management to
mod_fcgid.
--
Filip Hajny
--
On 28.2.2009, at 15:24, Olivier B. wrote:
> So, I simply read the file sapi/cgi/README.FastCGI in the PHP source.
> If I well understand, this feature is usefull when you run directly
> PHP
> as the fcgi daemon.
>
It's also useful when you want memory shared among the PHP processes
(e.g. for
On 28.2.2009, at 17:05, Olivier B. wrote:
> Yes I was thinking that but what is the interest to share memory
> between
> processes which never run simultaneously ?
>
They do. If you let PHP spawn them, they all start right away, and
keep running until you kill them. They are not killed when i
On 28.2.2009, at 17:27, Olivier B. wrote:
> my first question was about that : it seems that fcgid will _never_
> use
> this concurrent PHP instances. If there is 2 concurrent access, fcgid
> will spawn an other "group" of PHP to handle that, it will not use the
> first group of php instance whi
10 matches
Mail list logo
