Bug 60731 - PHP patch 4.0.6-12 breaks php-mysql
PHP patch 4.0.6-12 breaks php-mysql
Status: CLOSED DUPLICATE of bug 60515
Product: Red Hat Linux
Classification: Retired
Component: php (Show other bugs)
7.2
i386 Linux
high Severity high
: ---
: ---
Assigned To: Phil Copeland
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-03-05 13:43 EST by Nathan G. Grennan
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-03-05 13:43:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nathan G. Grennan 2002-03-05 13:43:28 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8+) Gecko/20020227

Description of problem:
mysql is set to refer to mysql.sock in /var/lib/mysql(mysql's home directory).
In the past it was set to /tmp, and /tmp is the mysql default. I believe this
change was made to clean up the /tmp directory and maybe add security. After
upgrading to php-*-4.0.6-12 it again tries to refer to mysql.sock in /tmp even
though the latest redhat mysql's my.cnf refers to it in /var/lib/mysql. This
will break any website that depends on php-mysql and is using the standard
configuration. Two workarounds are to either make a symlink from
/var/lib/mysql.sock to /tmp/mysql.lock, not a great way. Another is to change
/etc/my.cnf and change the socket= line.

Version-Release number of selected component (if applicable): 4.0.6-12

How reproducible:
Always

Steps to Reproduce:
1. Upgrade to php-*-4.0.6-12
2. Go to a url that depends on php to read data out of mysql
3. See the error message about no able to find /tmp/mysql.sock
	

Actual Results:  See the error message about no able to find /tmp/mysql.sock

Expected Results:  See no error message and the page to load normally.

Additional info:
Comment 1 Phil Copeland 2002-03-05 13:49:29 EST

*** This bug has been marked as a duplicate of 60515 ***

Note You need to log in before you can comment on or make changes to this bug.