Red Hat Bugzilla – Bug 60739
mysql, apache and php "mysql.sock" compatability link needed
Last modified: 2007-04-18 12:40:44 EDT
RH 7.2 after 2/2002 updates [root@landlocked etc]# rpm -qf my.cnf mysql-3.23.41-1 which includes the definition of the socket location: [root@landlocked etc]# cat my.cnf [mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock [mysql.server] user=mysql basedir=/var/lib [safe_mysqld] err-log=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid ---------- fails with a restart of apache ( apache-1.3.22-2 ) and php ( php-4.0.6-12 ) -- [had a overflow exploit ] ----------- Proposed action -- test for, and as needed add, in the post-isntall script for mysql: ln -s var/lib/mysql/mysql.sock /tmp (possibly consider adding to the apache and php packages as well) and restart mysqld, and apache mysql seems to be the proper package for this fix, because its conf file references /var/lib/mysql/mysql.sock
Bug in PHP - a triggerhappy autconf script decides to hardcode the location to /tmp. This is new. Reassigning so the PHP owner can mark it as a dupe :)
Is this wise to move this here? I had consciously placed it at mysql, for the my.cnf pointer to this file would be a normal diagnostic router for a puzzled sysadmin to check owning packagefor. That sysadmin would then (hopefully) query the owning package (mysql) and find (even if closed WONT) the answer which they needed. I have no problem with a WONT and leaving this at mysql -- I _do_ have a problem with it getting lost in the clutter at php as a DUPE -- Since you have transferred it with an intention that it be closed as DUPE, this implicitly says that you WONT as to the suggested fix. I'll re-position and close WONT
Tsk tsk,... check before you leap...
Note that the problem lies in php's configure check. *** This bug has been marked as a duplicate of 60515 ***