ID: 22101 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Analyzed Bug Type: Scripting Engine problem Operating System: Debian linux 2.4.19 PHP Version: 4.3.0 New Comment:
I wouldn't be surprised if an open_basedir set to / wasn't handled correctly. It is one of these non-sensical settings that I suppose we should account for, but it really is meaningless. All you are doing is burning more system calls with absolutely no benefit since everything is under / Previous Comments: ------------------------------------------------------------------------ [2003-02-06 19:58:56] [EMAIL PROTECTED] Warning: Unknown(): open_basedir restriction in effect. File(/www/htdocs/phpSysInfo-2.1/index.php) is not within the allowed path(s): (/) in Unknown on line 0 Warning: Unknown(/www/htdocs/phpSysInfo-2.1/index.php): failed to create stream: Operation not permitted in Unknown on line 0 Warning: Unknown(): Failed opening '/www/htdocs/phpSysInfo-2.1/index.php' for inclusion (include_path='.:/usr/lib/php') in Unknown on line 0 As you can see, /www is in my opinion, inside /, which is my open_basedir for this particular file. The Apache config for this directory: <Directory "/www/htdocs/phpSysInfo-2.1"> php_admin_value open_basedir "/" </Directory> You can get the phpSysInfo-2.1 script yourselves, too long to paste here, and it's not mine anyways. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=22101&edit=1
