Thanks for informing me that CGI and CLI may use a different php.ini and that
they may be compiled differently.
The admin finally admitted that he ran a yum update which overwrote the
manually compiled CLI version.
The reason I missed it was that the build date of the latest CLI version was
From: Chris [EMAIL PROTECTED]
Instruct ICC wrote:
You said something about 2 different configuration files. I'm just making
up this name, but do you have something like:
CLI_Configuration File (php.ini) Path = /etc/cli_php.ini
as well as:
Configuration File (php.ini) Path = /etc/php.ini
I
From: Chris [EMAIL PROTECTED]
Instruct ICC wrote:
Both your command
php -i | grep 'php.ini'
and
find / -name php.ini 2/dev/null
report the single /etc/php.ini
Hmm. do a php -i and look for:
Configuration File (php.ini) Path =
That will tell you where it's looking for the file.
Maybe you
However, a web page that includes the same file with the mssql_connect
call still works fine, and now it makes sense that I see mssql is still
enabled in phpinfo.
The apache version of the php.ini file is different to the cli version.
Make sure you are looking at the right one.
On debian I
I had cronjobs running fine on Linux which included a file which called
mssql_connect.
Today when I run the cronjob script directly from the command line, I get:
PHP Fatal error: Call to undefined function mssql_connect() in
/the/included/file.php on line #
Fatal error: Call to undefined
However, a web page that includes the same file with the mssql_connect
call still works fine, and now it makes sense that I see mssql is still
enabled in phpinfo.
The apache version of the php.ini file is different to the cli version.
Make sure you are looking at the right one.
On debian
