The correct way to deal with this is to edit /etc/my.cnf and, in the mysqld section set the location of the socket.

[mysqld]
socket = /tmp/mysql.sock

if there are other systems expecting it to be at the new location, a
simple end run might be to create a link at /tmp/mysql.sock -> /var/lib/mysql/mysql.sock.


 - michael dykman
 - [EMAIL PROTECTED]



Jough P wrote:
Greetings all,

I recently upgraded from mysql 3.23 to 4.0 on a Fedora box. I moved the old installation to a directory called old_mysql in my home directory. I can start the new installation using mysqld_safe &.

Now, when I try to do something like:
/new/install/mysqladmin -u root -p version

it says it can't connect because there is no /tmp/mysql.sock. And that is the case. The mysql.sock file is in /var/lib/mysql/mysql.sock

When I do something like:
old_mysql/mysqladmin -u root -p version
it can connect and, in fact, I can connect to the new mysql server by using old_mysql/mysql -u root -p


Should I just go on using the old clients? Why is there no /tmp/mysql.sock? How can I make mysql create one?

Help! and Thanks!!!




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to