Wrong socket

------_=_NextPart_001_01C67528.10F92D5C
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Greetings

I am running mysql 5.0.21 installed from source on a Dell PowerEdge 6450 =
with 4 dual-core Xeons running RedHat Enterprise v4.

I installed DBI 1.5 from source and DBD:mysql 3.003 from source.

mysql_config yields:

Usage: /usr/local/mysql/bin/mysql_config [OPTIONS]
Options:
--cflags [-I/usr/local/mysql/include/mysql]
--include [-I/usr/local/mysql/include/mysql]
--libs [-L/usr/local/mysql/lib/mysql -lmysqlclient -lz =
-lcrypt -lnsl -lm]
--libs_r [-L/usr/local/mysql/lib/mysql -lmysqlclient_r =
-lz -lpthread -lcrypt -lnsl -lm -lpthread]
--socket [/tmp/mysql.sock]
--port [3306]
--version [5.0.21]
--libmysqld-libs [-L/usr/local/mysql/lib/mysql -lmysqld -lz =
-lpthread -lcrypt -lnsl -lm -lpthread -lrt]

/etc/my.cnf also points to /tmp/mysql.sock.

If I try to access the database through the DBD/DBI perl interface on =
its host machine, it fails because it can't a socket at =
/var/lib/mysql.sock. I can't find a way to convince it that it should =
use /tmp/mysql.sock. The documentation says it uses the client's =
definition, but that should be /tmp/mysql.sock. I found on the =
mysql:install forum that one can use 127.0.0.1 rather than localhost and =
this in fact works OK. But, can someone tell how to affect where DBD or =
DBI looks for the socket?

Thanks

Mike

------_=_NextPart_001_01C67528.10F92D5C--