Re: PHP_INI_SCAN_DIR or PHPIniScanDir
| From: | Richard Quadling | Date: | Thu, 09 Jun 2011 00:04:31 +0000 |
| Subject: | Re: PHP_INI_SCAN_DIR or PHPIniScanDir | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-313475@lists.php.net to get a copy of this message | ||
On 9 June 2011 00:18, Lester Caine <lester@lsces.co.uk> wrote:
> Richard Quadling wrote:
>>
>> On 8 June 2011 22:59, Richard Quadling<rquadling@gmail.com> wrote:
>>>
>>> But there is a tiny bug in php.
>>> The php --ini output doesn't reflect the PHP_INI_SCAN_DIR setting.
>>
>> http://bugs.php.net/bug.php?id=48831
>>
>> Reported but only partially fixed. As I was using my own builds, I
>> didn't realise the full patch hadn't been committed.
>>
>> New laptop. Using standard builds. Saw the error.
>
> Ditto on new laptop ... I've not got the M$ build enviroment working yet all
> my own work is on 'Borland' as was so I've got to get that working fully
> first :(
>
> Your command line stuff works, but I only use PHP with Apache. I've got a
> 'SetEnv PHP_INI_SCAN_DIR xxx' before the module load, but it's not reporting
> any extra ini's
> Do I need to compile with something else set - not that I can compile at all
> at the moment, I'm working with pre built binaries.
I can see that the CGI SAPI uses this properly.
Change the code I get so that you run php-cgi rather than php
There is no --ini option, but the -i should work, though the output
will be HTML.
--
Richard Quadling
Twitter : EE : Zend : PHPDoc
@RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea