MySQL startup ignores socket directive
I am facing a strange behaviour when trying to setup a node which has 2 different versions of mysql running. The second instance tends to ignore the "socket" directive and uses /tmp/mysql.sock instead of the defined /tmp/<hostname>.sock. The system has multiple virtual interfaces and conflict is not the issue.
bash-3.00# /global/db/bin//mysqld --defaults-file=/global/db/my.cnf
--user=root --pid-file=/global/db/logs/my.pid --basedir=/global/db/
--datadir=/global/db/ &
[1] 13773
bash-3.00# 090427 12:09:40 InnoDB: Started; log sequence number 0 46409
090427 12:09:40 [Note] Event Scheduler: Loaded 0 events
090427 12:09:40 [Note] /global/db/bin//mysqld: ready for connections.
Version: '5.1.24-rc' socket: '/tmp/mysql.sock' port: 3306 MySQL
Community Server (GPL)
The datadir is owned by the mysql user and problem occurs even if the datadir and the basedir are different.
If you have an idea on what the problem might be, please drop me a note.