php.ini and ownership

[Lcousins]

Hi, wandered over here from the newbie forum in the hope of getting some specialist help:D

I have php and MySQL installed apparently totally corrrectly with the exception that no MySQL fuctions work with the PHP.

the solution ive been given is to edit the php.ini file and add a few lines telling it to use the MySQL extension and ading its location. Now Ive located the file through ftp logged in as server admin, but am told I dont have permission to edit it.

what I need to know is whats the best way for me to edit this file, why the admin wouldnt have the right permissions and what I can do about it, all answers written so that I as a bit of a hopeless beginner can understand.

thanks

Luke

[dalecosp]

Permissions. Hmm. A problem indeed.

If the admin has them set that way, he's either mistaken, or ignorant of your needs, or else he wants them that way. I'd suggest direct communication, and maybe something to help the process along. Are you friends? Become so.....

As to the problem itself, in Apache, sometimes php.ini directives can be placed in a .htaccess file in your directory. Many of them would augment or override settings in php.ini

OTOH, I'm kinda wondering if the premise here is correct. If PHP doesn't grok MySQL functions, I'd suspect the compile process first. And, if you're not the admin, that will definitely be an issue....

G'luck :)

[Lcousins]

Hi,

well an update to this one, I am the admin, I rent the server (dedicated) from one of the big names, who have now solved half the problem in that theyve gone in and changed the extensions in php.ini . They avoided the question of why I, as the supposed owner of the server dont seem to have access to it but at least it all works now which was the most important thing!!:D

I think what I am after, which I failed to make clear in my first post was a way to find out what user does have permissions on that particular file and whether I, going in as root can change this. I actually went for a vary highly priced package when i chose the server to avoid all this, as command line linux isnt my strong point but hey ho, I live and learn :rolleyes:


m.

[jerdo]

To access files like that you might have to ssh in as admin and then su. If they gave you root access you should be good to go.

[dalecosp]

If they're giving you some web-based GUI, i.e. V-admin Suite or somesuch, it could very well be that THEY aren't letting the "web user" (in the case of Apache, often 'nobody' or 'www') have root privileges.

Might as well brush up on the CLI in that case, as Jerdo has observed...