ID: 14401
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: *Configuration Issues
Operating System: Linux i386
PHP Version: 4.1.0
New Comment:

Having looked somewhat deeper into this issue I want to add
that the include path problem seems limited to include files
that get loaded via the auto_prepend_file directive.
Explicit "include" or "require" statements seem to work
as they should.  But please take this with a grain of salt,
because this may be a result of the fact that files with
auto_prepend_file-loaded headers have far more hits than
those with explicit "include"s.


Previous Comments:
------------------------------------------------------------------------

[2001-12-10 08:51:33] [EMAIL PROTECTED]

We have a virtual host here where the include_path varies
per directory.  We configure this in the Apache config
(php as a DSO module) like this:

<Directory /var/www/html/dir1>
  php_value include_path ".:/var/www/html/dir1/lib"
</Directory>
<Directory /var/www/html/dir2>
  php_value include_path ".:/var/www/html/dir2/lib"
</Directory>
(and many more)

We have tried this with many versions of Apache 1.3.x
and php-4.0.x (up to apache-1.3.22 / php-4.1.0RC3) and
all combinations exhibit the same problem:  If there are
two or more concurrent users that access different
directories of this virtual host, one or more of them get
pages with php errors, because the php scripts don't
get the include files they need.  The error messages show
clearly that the include files were searched via a wrong
include_path, i.e. one out of the other <Directory ..>
sections of the same virtual host.

We used both standard Redhat 7.x apache and php RPMs, as
well as self-compiled RPMs based on Redhat's SRPMs, all
with the same result/problem.

If you need more specific information, please ask.


------------------------------------------------------------------------



Edit this bug report at http://bugs.php.net/?id=14401&edit=1


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to