i hear all time edit the php.ini. i just got vps and for first time have root access. where the hell is the php.ini i have never needed to edit it.

Depends on the installation, but generally usr/local/bin/php.ini

you can try with this command: locate php.ini

mine is also found in: /usr/local/lib/php.ini

if you are not familiar with linux command line may be you can use whmxtra (http://whmxtra.com/) for editing system files. it is very helpful. just an advice.

is there a free software like whmxtra

i just got vps

On a vps, most likely you're not going to have access to something like php.ini, because vps is a virtual private system. Not really a dedicated server, this environment typically does not have a separate php install for each vps, but a global one , per server.

Of course, this can depend on the provider of the vps themselves.

You sure about that? What would be the point of having one PHP install per server, when you have the ability to add Zendopt and other items? Having one "master" install would mean that I could break someone else's PHP scripts by changing settings.

On Servint, I can edit php.ini, install or remove Zend, or whatever I need. I have root, and my changes affect only my VPS.

The easiest way to find out the location to your php.ini file, is to create a blank page on your webserver with this line:

<?php phpinfo(); ?>

When you browse to that page, it will give you all the information you need about your PHP install, including what modules are available, and where the php.ini file is located -- more importantly, it will tell you the one that Apache is using. There can be more than on php.ini file on the system, and it will be very frustrating for you if you find out your changes aren't taking effect because you have been editing the wrong one.

On a vps, most likely you're not going to have access to something like php.ini, because vps is a virtual private system. Not really a dedicated server, this environment typically does not have a separate php install for each vps, but a global one , per server.

Of course, this can depend on the provider of the vps themselves.

That's wrong. A true VPS has separate software installs (and in fact separate OSes for) for every VPS.. It's one of the things that makes 'em so inefficient. If there isn't a septate OS, a separate Apache, a separate MTA.. It's not a VPS.

-Jason

i hear all time edit the php.ini. i just got vps and for first time have root access. where the hell is the php.ini i have never needed to edit it.

php.ini can be in several places. There is a global php.ini (use the phpInfo() idea from above to find out where it is). There is no one standard place. (Zend moves it to it's own tree, different installs default to different places).

In some hosting environments (php as suexec I think), each directory in the web tree can have it's own php.ini and unlike .htaccess it generally does not effect the directories below it.

for example

you can put a php.ini in /public_html that will override the global php.ini. /public_html/dir2 would not be effected by the /public_html/php.ini but it could have it's own.

This is a problem when you have a big installation that requires register_globals be turned on and the global php.ini has them turned off (like it should).

You need to put a php.ini in every directory that you will be running php scripts from.

-Jason