cpanel overwriting php.ini

[tifosi]

Hi

This has been happening since the upgrade to cpanel 11.x.

Cpanel is continually overwriting php.ini nightly and altering the extension_dir configuration value to one which is wrong... using /usr/lib... instead of /usr/local/lib...

Really I don't want CPANEL touching php.ini at all!

php 5.2.3 was configured initially using cpanel and then I recomplied it with a custom configuration and included values for eaccelerator.

I've tried numerous things... chmodding cpanels checkphpini & phpsanitycheck scripts, but they get updated prior to use.

I just can't figure out where it's getting this extension_dir from since everything else uses /usr/local including php-prefix.

any advice on where to find this...

S

[cpanelkenneth]

/scripts/updatephpconf

What is the result of this:

php-config --extension-dir

[tifosi]

Thanks for the reply

the output is as expected: and --prefix is /usr/local

/usr/local/lib/php/extensions/no-debug-non-zts-20060613

But cpanel reset it to

/usr/lib/php/extensions/no-debug-non-zts-20060613

which then of course lost the path to the eaccelerator

I've created a symbolic link as a workaround.

[cpanelnick]

/usr/local is prefered over /usr now in 14684+


It shouldn't change the ext dir unless it set to a dir that doesn't exist.



sub get_extension_dir {
my $path = get_directive('extension_dir');
if ( !$path || $path eq './' || $path eq '/' || $path eq '.' ) {
# this seems to break improperly installed ioncube
set_extension_dir();
$path = get_default_extension_dir();
}
return ($path ne './') ? $path : get_default_extension_dir();
}

[tifosi]

That was the problem I think.

I set the extension_dir to "" which it has accepted in he past.

I've now reset it to the compiled exension_dir of /usr/local.... & modified a few other paths and all is ok.

Wonder if is used the /usr because there's a very old php4 manual install directory at that level even though the active php5 is in /usr/local

Hopefully useful to others who may come across this.

[kris1351]

Odd, ours did a change with last nights update also. It didn't change the directories, just the number of the extension directory it was looking for.