Pure-ftpd-mysql socket error after latest mysql update [SOLVED]

Question

As we know the socket path in mysql have been moved from /tmp/mysqld.sock to /var/run/mysqld/mysqld.sock.
The problem now with pure-ftpd-mysql is that it tries to use /tmp/mysqld.sock even though I have:
MYSQLSocket /var/run/mysqld/mysqld.sock
Inside of my /etc/pure-ftpd/pure-ftpd-mysql.conf
I guess that either MYSQLSocket is the wrong keyword or that the path is hard coded into pure-ftpd-mysql.
Any ideas how to solve this?
EDIT:
The path for the mysql conf was changed during last update
from
MySQLConfigFile  /etc/pure-ftpd/pure-ftpd-mysql.conf
to
MySQLConfigFile /etc/pure-ftpd/auth/mysql.conf
Last edited by ancide (2009-11-25 10:23:24)

Answer 1

maksvlad wrote:
I've edited /etc/rc.d/mysqld file and added "ln -fs /var/run/mysqld/mysqld.sock /tmp/mysql.sock" like this
echo $(getPID) >/var/run/mysqld/mysqld.pid
add_daemon mysqld
ln -fs /var/run/mysqld/mysqld.sock /tmp/mysql.sock
stat_done
It isn't  correct solution but it works...
On other hand you would try something like this http://bbs.archlinux.org/viewtopic.php?id=85441
Thanks for the reply. The problem is that all my other applications are using the new correct path. But I guess I can just make a symlink like you said for now until pure-ftpd-mysql is fixed.