One feature of php 5.3 that I was waiting for is this one from
php.ini:

[PATH=/var/www/my.domain.com]
max_execution_time=1
memory_limit=8MB
open_basedir=/var/www/my.domain.com
doc_root=/var/www/my.domain.com


Every thing works fine, except that one I put open_basedir, I start to
get random messages like: "No input file specified."
if I remove open_basedir, it back to works normally.

Has anybody tested this feature?

what webserver are you using, just for kicks?

On Thu, Jul 16, 2009 at 4:43 AM, Neves<marcos.neves@gmail.com> wrote:
>
> One feature of php 5.3 that I was waiting for is this one from
> php.ini:
>
> [PATH=/var/www/my.domain.com]
> max_execution_time=1
> memory_limit=8MB
> open_basedir=/var/www/my.domain.com
> doc_root=/var/www/my.domain.com
>
>
> Every thing works fine, except that one I put open_basedir, I start to
> get random messages like: "No input file specified."
> if I remove open_basedir, it back to works normally.
>
> Has anybody tested this feature?

Is there a way you can test a normal non-FPM version with this?

I don't believe the FPM patchwork should change this behavior (of
course, I've been wrong many times)

On Thu, Jul 16, 2009 at 4:43 AM, Neves<marcos.neves@gmail.com> wrote:
>
> One feature of php 5.3 that I was waiting for is this one from
> php.ini:
>
> [PATH=/var/www/my.domain.com]
> max_execution_time=1
> memory_limit=8MB
> open_basedir=/var/www/my.domain.com
> doc_root=/var/www/my.domain.com
>
>
> Every thing works fine, except that one I put open_basedir, I start to
> get random messages like: "No input file specified."
> if I remove open_basedir, it back to works normally.
>
> Has anybody tested this feature?

I

Sure. Well it's good to know it's not localized to fpm.

I'm thinking when you do that the script filename changes, and you may
have to alter the fastcgi_param in nginx...


On Thu, Jul 16, 2009 at 11:54 AM, Neves<marcos.neves@gmail.com> wrote:
>
> I´ve tried with spawn-fcgi too, and the same problem happens.
> I just want to share this with you.
>
> On 16 jul, 14:05, Michael Shadle <mike...@gmail.com> wrote:
>> Is there a way you can test a normal non-FPM version with this?
>>
>> I don't believe the FPM patchwork should change this behavior (of
>> course, I've been wrong many times)
>>
>>
>>
>> On Thu, Jul 16, 2009 at 4:43 AM, Neves<marcos.ne...@gmail.com> wrote:
>>
>> > One feature of php 5.3 that I was waiting for is this one from
>> > php.ini:
>>
>> > [PATH=/var/www/my.domain.com]
>> > max_execution_time=1
>> > memory_limit=8MB
>> > open_basedir=/var/www/my.domain.com
>> > doc_root=/var/www/my.domain.com
>>
>> > Every thing works fine, except that one I put open_basedir, I start to
>> > get random messages like: "No input file specified."
>> > if I remove open_basedir, it back to works normally.
>>
>> > Has anybody tested this feature?

I dont think that could be nginx, but I would like to debug the
comunication between nginx and fcgi.
What tool can I use? I try this one http://cgit.stbuehler.de/gitosis/fcgi-debug/
but I couldnt compile it.

On 16 jul, 15:57, Michael Shadle <mike...@gmail.com> wrote:
> Sure. Well it's good to know it's not localized to fpm.
>
> I'm thinking when you do that the script filename changes, and you may
> have to alter the fastcgi_param in nginx...
>
>
>
> On Thu, Jul 16, 2009 at 11:54 AM, Neves<marcos.ne...@gmail.com> wrote:
>
> > I

no clue, but it sounds like it changes how the script_filename is
done. perhaps turn on debug on nginx, and see what SCRIPT_FILENAME
says (it should still be the same) but due to the basedir you might
need to take out $document_root and only put in $script_name (perhaps
open_basedir is essentially chrooting things?)



On Thu, Jul 16, 2009 at 12:40 PM, Neves<marcos.neves@gmail.com> wrote:
>
> I dont think that could be nginx, but I would like to debug the
> comunication between nginx and fcgi.
> What tool can I use? I try this one http://cgit.stbuehler.de/gitosis/fcgi-debug/
> but I couldnt compile it.
>
> On 16 jul, 15:57, Michael Shadle <mike...@gmail.com> wrote:
>> Sure. Well it's good to know it's not localized to fpm.
>>
>> I'm thinking when you do that the script filename changes, and you may
>> have to alter the fastcgi_param in nginx...
>>
>>
>>
>> On Thu, Jul 16, 2009 at 11:54 AM, Neves<marcos.ne...@gmail.com> wrote:
>>
>> > I´ve tried with spawn-fcgi too, and the same problem happens.
>> > I just want to share this with you.
>>
>> > On 16 jul, 14:05, Michael Shadle <mike...@gmail.com> wrote:
>> >> Is there a way you can test a normal non-FPM version with this?
>>
>> >> I don't believe the FPM patchwork should change this behavior (of
>> >> course, I've been wrong many times)
>>
>> >> On Thu, Jul 16, 2009 at 4:43 AM, Neves<marcos.ne...@gmail.com> wrote:
>>
>> >> > One feature of php 5.3 that I was waiting for is this one from
>> >> > php.ini:
>>
>> >> > [PATH=/var/www/my.domain.com]
>> >> > max_execution_time=1
>> >> > memory_limit=8MB
>> >> > open_basedir=/var/www/my.domain.com
>> >> > doc_root=/var/www/my.domain.com
>>
>> >> > Every thing works fine, except that one I put open_basedir, I start to
>> >> > get random messages like: "No input file specified."
>> >> > if I remove open_basedir, it back to works normally.
>>
>> >> > Has anybody tested this feature?