Bug 477668
Summary: | PHP include_path incorrect | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | HostMySite.com <vendor> |
Component: | php | Assignee: | Joe Orton <jorton> |
Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE <qe-baseos-auto> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.4 | CC: | vendor |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-01-07 11:47:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
HostMySite.com
2008-12-22 19:46:10 UTC
Thanks for the report. With the default php.ini you should get output as follows: [root@dhcp-0-199 ~]# grep include_path /etc/php.ini ; (directory must also be in include_path or full path must ;include_path = ".:/php/includes" ;include_path = ".;c:\php\includes" Please post the output of: # rpm -q php # rpm -V php from this system. [root@serve r~]# grep include_path /etc/php.ini ; (directory must also be in include_path or full path must include_path = ".:/php/includes" ;include_path = ".;c:\php\includes" [root@server ~]# rpm -q php php-5.1.6-20.el5_2.1 [root@server ~]# rpm -V php S.5....T c /etc/httpd/conf.d/php.conf Ah, actually, the correct rpm -V command to run should be: rpm -V php-common it looks pretty clear /etc/php.ini is modified from the default on this box, in any case. Just checked a fresh server: [root@ninja ~]# grep include_path /etc/php.ini ; (directory must also be in include_path or full path must ;include_path = ".:/php/includes" ;include_path = ".;c:\php\includes" [root@ninja ~]# cat /etc/issue Red Hat Enterprise Linux Server release 5.2 (Tikanga) Kernel \r on an \m Must be our deploys that are causing the problem. This report can be closed. Thanks for reporting back! |