That link came up non-existent, but I checked the mysql site and found the published solution about checking for the existence of the .sock file and moving it if it's in the wrong place.
So, I found that there was mysql.sock in /private/tmp, but the error indicates it's being looked for in /opt/local/var/run/mysql5, so I moved it there, and I changed the group from 'wheel' to '_mysql'.
Once moved, mysql would not start. I did a 'which -a "mysql5"' and it is in /opt/local/bin. However, moving the .sock file back to /private/tmp immediately caused mysql to start again.
So, the question is if mysql is looking for the .sock file in the port path, and the mysql process running is from the port path, why does having the socket where it's being looked for break mysql rather than allowing me to run the command line program?
Your best bet is to read the official MySQL reference docs at:
<http://dev.mysql.com/doc/refman/5.5/en/connecting-disconnecting.html>;
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
