ID: 22189 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Bogus +Status: Open Bug Type: *Configuration Issues Operating System: Linux 2.2 / 2.4 PHP Version: 4.3.0 New Comment:
Thanks for the answer but I think might you have missed the point so let me put this in another context: Some slightly insane sysop wants php.ini to reside here: /etc/php.ini/php.ini and uses the following config line to specify the path: '--with-config-file-path=/etc/php.ini' phpinfo() will show for Configuration file: '/etc/php.ini' instead of '/etc/php.ini/php.ini' which would be the correct location. The problem might be with phpinfo then: you put the config file where PHP says it loads it from, but it doesn't load it. Well at least in this insane case when you choose such a location. Previous Comments: ------------------------------------------------------------------------ [2003-02-12 12:12:29] [EMAIL PROTECTED] Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php Your assumption is quite correct, this option needs to be only passed the directory where the php.ini can be found not the path to the file itself. ------------------------------------------------------------------------ [2003-02-12 10:57:52] [EMAIL PROTECTED] Something is probably wrong with intrepreting the following configure option: '--with-config-file-path=/usr/local/apache/conf/php.ini' phpinfo() will report this: Configuration File (php.ini): "/usr/local/apache/conf/php.ini" This is exactly the same as if you compile it with a saner option: '--with-config-file-path=/usr/local/apache/conf/' The difference between the two cases is that in the first case the config file is not loaded by PHP. My educated guess is that it tries to load if from: "/usr/local/apache/conf/php.ini/php.ini" so it fails and the location is simply misreported in phpinfo(). I fisrt met this a long ago with 4.0.6 or 4.1.2 or so, but it's still there in 4.3.0 as I just ran into this type of a problem again. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=22189&edit=1
