Re: [cobalt-users] Qube3-All-Security-4.0.1-15959.pkg

[Malcolm McLeary <mmcleary@xxxxxxx>]

Hi Greg,

on 7/4/03 9:31 AM, Greg Hewitt-Long wrote:

> I can't swear to it being related, as I installed a number of patches at the
> same time as 15959.pkg, but I had PHP quit working completely (install a
> simply php script which just prints hello world, or phpinfo() or something to
> check.

Comparing phpinfo() on a pre and post Qube3-All-Security-4.0.1-15959.pkg
installation, I find that before applying the update phpinfo() reports;

MYSQL_SOCKET    /var/lib/mysql/mysql.sock

but after the update phpinfo() reports;

MYSQL_SOCKET    /tmp/mysql.sock

This would appear to be a significant change which would cause problems.

I wonder where this is defined ... and why it was necessary to change it.

In the meantime I have created a symbolic link from /tmp/mysql.sock to
/var/lib/mysql/mysql.sock and I'm able to reach the main page for phpBB once
again.

Is Qube3-All-Security-4.0.1-15959.pkg responsible for this change?  I can't
think of anything else I've done to these machines.

I've just been for a poke around a couple of other Qube3s I have access to
and find the same results.  Those with Qube3-All-Security-4.0.1-15959.pkg
installed have;

MYSQL_SOCKET    /tmp/mysql.sock

those without Qube3-All-Security-4.0.1-15959.pkg installed have;

MYSQL_SOCKET    /var/lib/mysql/mysql.sock

Given that the standard Qube3 version of php.ini has the mysql module
disabled I fail to see why Sun decided to change this parameter.

Cheers,  Malcolm