Did location of mysql.sock change in mysql5.0.37?

[Bakki Kudva]

On 5/7/07, Emory Smith <emory.smith at gmail.com> wrote:
>
> are you sure the mysql5 daemon is running? (try running "ps aux |
> grep mysqld")

Yes it is running and I can connect to it form the command line.

> if you really just did "port upgrade", its probably still the mysql4
> daemon running on the envirnment thats working.

This machine never had mysql4, so it was an upgrade from a previous
5.x.x version.

> if so, youll probably need to kill it manually with "sudo killall
> mysqld_safe" (assuming mysql4 was deactivated).

Since the upgrade i had to reboot the machine because of an apple
security update so correct daemon is running...also I did deactivate
and uninstall the previous version.

I can set the socket path in Rails databases.yml file but when this
gets checked into subversion all the other machines which are running
fine with socket at /tmp will have problems. So I guess I will have to
tell mysql5 to use /tmp for socket by setting the my.conf file. The
strange thing though is that the same setup (no my.cnf and the same
versions of mysql5 and the rails app) is working fine on my
MacbookPro. Before I set the my.conf file I just want to understand
what's going on...right now it is not knowing that's bothering me.

-bakki