2 messages in com.mysql.lists.mysqlMySQL DBD not following my.cnf for so...
FromSent OnAttachments
Sid Lane13 Jan 2005 07:47 
Ian Gibbons13 Jan 2005 08:02 
Subject:MySQL DBD not following my.cnf for socket file
From:Sid Lane (jake@gmail.com)
Date:01/13/2005 07:47:00 AM
List:com.mysql.lists.mysql

hope this isn't considered too off-topic but...

I have been working on standardizing the directory trees on our MySQL servers (a la OFA for those who speak Oracle) but when I repoint the socket parameter in my.cnf all my perl scripts barf w/:

"Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) at ./somescript.pl line 666"

I can connect from a shell w/the mysql client no problem. it's only DBD that's having this problem and pointing socket back in my.cnf and restarting mysql fixes it which leads me to believe this is statically configured into DBD when you build it.

does anyone know if this is the case? is there anything short of rebuilding DBD that will get it to use the new location?

any help would be appreciated.