7 messages in com.mysql.lists.perlFW: Problems with mysql.sock
FromSent OnAttachments
michael watson (IAH-C)15 Sep 2003 05:50 
Jochen Wiedmann15 Sep 2003 06:02 
michael watson (IAH-C)15 Sep 2003 06:05 
Jochen Wiedmann15 Sep 2003 06:17 
michael watson (IAH-C)15 Sep 2003 06:19 
Ulrich Borchers15 Sep 2003 06:33 
Rudy Lippan15 Sep 2003 07:39 
Subject:FW: Problems with mysql.sock
From:michael watson (IAH-C) (mich@bbsrc.ac.uk)
Date:09/15/2003 05:50:22 AM
List:com.mysql.lists.perl

Hi

I need to know how and where to tell mysql to look for mysql.sock.

I am using mysql version 3.23.55 and SUSE Linux 8.2.

My problem is that i have a mysql daemon working very well and using
/var/lib/mysql/mysql.sock as the correct socket. No problems.

My problems come when I try and install the perl msql-mysql modules.

It asks for my mysql directory, which is /usr/local/mysql/.

I can only assume that it then tries to execute /usr/local/mysql/bin/mysql, and
guess what? For some reason it tries to connect through the default
/tmp/mysql.sock, which doesn't exist and everything fails.

SO whats going on? Why, when i execute /usr/bin/mysql does mysql look to
/var/lib/mysql/mysql.sock and when I execute /usr/local/mysql/bin/mysql, does it
look to /tmp/mysql.sock? How can I set BOTH to look at
/var/lib/mysql/mysql.sock?

I tried mysql_config --socket /var/lib/mysql/mysql.sock, but all that does is
repeat the usage message for mysql_config.

So when I try to connect through DBI, I get a "cannot connect through
/tmp/mysql.sock" error message. But the mysql on my computer, the daemon that
is up and running, always connects through /var/lib/mysql/mysql.sock. I even
have that set in /etc/my.cnf.

Help me, I am confused!

Thanks Mick