Mark Sargent wrote:
ok, I don't fully understand why, but, mysql is still installed in /usr/bin. What I've done, just for now, is renamed mysql in that dir to mysqlold. I've added /usr/local/mysql/bin to my path. I then tried the cmd mysql and also ./mysql from within the dir /usr/local/mysql/bin, and after entering the correct password, I get the following,
[EMAIL PROTECTED] bin]# ./mysql -p
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
If I run ./usr/bin/mysqlold I can connect. What am I not understanding with this..?
If it were me, I'd remove all traces of mysql* anything from the system and start fresh. :-)
But in any case, which mysqld process is now running? I'm guessing it's the old one. If so, kill it, and start up your new version using an unambiguous path (e.g., /usr/local/mysql/bin/mysqld_safe).
Then try to connect with your new client.
HTH, -- Hassan Schroeder ----------------------------- [EMAIL PROTECTED] Webtuitive Design === (+1) 408-938-0567 === http://webtuitive.com
dream. code.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
