php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #6244 Files are not being included; parts of php.ini not being parsed
Submitted: 2000-08-18 14:39 UTC Modified: 2000-08-23 09:03 UTC
From: phil at cmc dot ca Assigned:
Status: Closed Package: Scripting Engine problem
PHP Version: 4.0 Latest CVS (18/08/2000) OS: Solaris 8
Private report: No CVE-ID: None
View Developer Edit
 [2000-08-18 14:39 UTC] phil at cmc dot ca 
When including the PEAR DB interface, PHP complains that it failed to open the file for inclusion.  It's in the include path, and is world readable.  It works fine if I switch back to v4.0.1pl2 without changing anything else.

php.ini has:
include_path='.:/keeper/web/server/php/lib/php'  (which is where the PEAR files are)

But when executing a script with the line:
include('DB.php');

The following error is displayed:
Warning: Failed opening 'DB.php' for inclusion (include_path='.:/keeper/web/server/php/lib/php') in header.inc.php on line 345

Also, a couple options that are set in php.ini aren't taking.. example:

php.ini has:
upload_max_filesize = 9999999999;

but a phpinfo() shows:
upload_max_filesize = 2097152 for both local and master

I'm using PHP as an ISAPI module under Zeus.
If you'd like any more information, feel free to contact me.

Phil

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2000-08-18 14:43 UTC] chagenbu@php.net 
I had the same problem, and for some reason, switching the order of the include path - ie, for you, to:
include_path = /keeper/web/server/php/lib/php:.

... solved the problem. No idea why, though...
 [2000-08-18 15:10 UTC] phil at cmc dot ca 
Tried switching them, and found it wasn't taking.  It seems that the include path is being compiled right into the binary, and not taken from the php.ini file.
 [2000-08-23 05:06 UTC] hholzgra@php.net 
i had a similar problem yesterday (bug #6302) 
and found out that php.ini worked as expected
when i started apache in single-process mode
with option -X for debugging reasons but that
it totaly ignored php.ini in its normal
multiprocess mode of operation

could you please try if you get the same effect
when starting apache with 'httpd -X' ?
 [2000-08-23 09:03 UTC] phil at cmc dot ca 
I'm actually using Zeus, not Apache.

I updated my copy of the code late Sunday evening
(2000-08-20) and that snapshot has been working fine.  I
also removed any old php.ini files on the system before
compiling it, as the snapshot from the 18th seemed to be
compiling some options from the existing config file right
into the new binary.
 
PHP Copyright © 2001-2026 The PHP Group
All rights reserved. 		Last updated: Sun Oct 11 10:00:01 2026 UTC