#20887 [Com]: /php.ini

ID: 20887 Comment by: michael.mauch@gmx.de Reported By: oden.eriksson@linux-mandrake.com Status: Open Bug Type: Unknown/Other Function Operating System: Mandrqke Linux 9.0 PHP Version: 4.3.0RC2 New Comment: I can't see that /php.ini is used here, but php/php-cli.ini is used, i.e. a file relative to the place from where PHP was started. With PHPRC=/xizzy I get: # strace -eopen php -r 'echo "bla";' 2>&1|grep ini open("php/php-cli.ini", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/xizzy/php-cli.ini", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) open("/usr/local/lib/php-cli.ini", O_RDONLY|O_LARGEFILE) = 3 open("/usr/local/lib/php/browscap/browscap.ini", O_RDONLY|O_LARGEFILE) = 3 And if php/php-cli.ini is there, PHP only reads that one. This is with 4.3.0-cvs from today, and I don't have Mandrake here (once upon a time, it was a SuSE Linux). Previous Comments: ------------------------------------------------------------------------ [2002-12-08 14:53:59] oden.eriksson@linux-mandrake.com If /php.ini exists, that one is used no matter what PHPRC env is set or compiled in when starting up apache from a SysV script. Is it a bug in php, or could it be the Mandrake Linux 9.0 system? ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=20887&edit=1