Which httpd.conf and php.ini files does plesk use

[Saif Bechan]

If i disable the include_path in /etc/php.ini, i can still see that there is an include path loaded from somewhere. I want to know where this file is.

If i use phpinfo(); on my domain i get that there is a include path /usr/share/pear:/usr/share/php, even though in the php.ini i used:

;inlucde_path=".:"

In the section for aditional php.ini files this is the list:

/etc/php.d/curl.ini,
/etc/php.d/dbase.ini,
/etc/php.d/dom.ini,
/etc/php.d/gd.ini,
/etc/php.d/imap.ini,
/etc/php.d/json.ini,
/etc/php.d/mbstring.ini,
/etc/php.d/mysql.ini,
/etc/php.d/mysqli.ini,
/etc/php.d/pdo.ini,
/etc/php.d/pdo_mysql.ini,
/etc/php.d/pdo_sqlite.ini,
/etc/php.d/wddx.ini,
/etc/php.d/xmlreader.ini,
/etc/php.d/xmlwriter.ini,
/etc/php.d/xsl.ini,
/etc/php.d/zip.ini

I have checked all these files but i can nowhere find a reference to pear.


This said the /etc/httpd/conf/httpd.conf file is questioning to me too. If i check this file i can see the following values are defined.

DocumentRoot "/var/www/html"

<Directory />
Order Deny,Allow
Deny from all
Options None
AllowOverride None
</Directory>

<Directory "/var/www/html">
Options None
AllowOverride None
Order allow,deny
Allow from all
</Directory>


the strange thing is that i don't even use this directory, so where does PLESK get his httpd.conf file from. I want to check if everything is ok, because my vhost.conf is not working.

I don't know if i should change these values or not, and where i can find the values PLESK uses. i hope someone can help me with this.

 

[IgorG]

Plesk Panel interface php:

/usr/local/psa/admin/bin/php
/usr/local/psa/admin/conf/php.ini

Client's php:

/usr/bin/php
/etc/php.ini


Config of Plesk sw-sp-server - /etc/sw-cp-server/applications.d/plesk.conf
Config of client's Apache - /etc/httpd/conf/httpd.conf

 

[Saif Bechan]

Thank you for the reply IgorG. It is al clear to me now. Everything seems to be ok now, it was setting of FastCGI which led to the ignorance of the vhost.conf values.

I hope there will be a good solution to this problem soon. Until then I will just stick with running php as an apache module.