open_basedir error when trying to set error_reporting through ini

open_basedir error when trying to set error_reporting through ini_set

Bug #25895

open_basedir error when trying to set error_reporting through ini_set

Submitted:

2003-10-17 07:02 UTC

Modified:

2005-01-31 22:43 UTC

Votes:	1
Avg. Score:	5.0 ± 0.0
Reproduced:	1 of 1 (100.0%)
Same Version:	1 (100.0%)
Same OS:	0 (0.0%)

From:

support at spill dot nl

Assigned:

iliaa (profile)

Status:

Closed

Package:

Safe Mode/open_basedir

PHP Version:

4.3.3

OS:

RHL 8.0

Private report:

CVE-ID:

None

[2003-10-17 07:02 UTC] support at spill dot nl

Description:
------------
When trying to run the posted code, I get the following (nonsense) error:

PHP Warning:  ini_set(): open_basedir restriction in effect. File(2047) is not within the allowed path(s): (/usr/share/pear/) in /home/admins/matthijs/test.php on line 3


Conditions:

- Occurs only when the php script itself is located in a path not contained in open_basedir (as you can see I do not have '.' in my open_basedir path).

- Calling 'error_reporting(E_ALL);' instead does not produce this warning.

- Tested only on: PHP 4.3.3 (cli)


Reproduce code:
---------------
<?php

ini_set("error_reporting",E_ALL);

?>


Expected result:
----------------
no output, no warnings, error level set to the level indicated

Actual result:
--------------
PHP Warning:  ini_set(): open_basedir restriction in effect. File(2047) is not within the allowed path(s): (/usr/share/pear/) in /home/admins/matthijs/test.php on line 3

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports

[2003-10-17 09:01 UTC] sniper@php.net

Short test:

# sapi/cli/php -dopen_basedir=/foobar -r 'ini_set("fooba_foo", "foooo");'

[2003-10-19 21:59 UTC] iliaa@php.net

This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at http://snaps.php.net/.
 
In case this was a documentation problem, the fix will show up soon at
http://www.php.net/manual/.

In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites in short time.
 
Thank you for the report, and for helping us make PHP better.