I stopped mysql, renamed the other 3 cnf files to cnf.old, and restarted it. It is still using the sock in /private/tmp even though the only cnf file points to /opt/local. I'm at a loss...should I grep for /private/tmp to try and find where it's buried??
-------- Original Message --------
Subject: Re: mysql problem with socket
From: Ryan Schmidt <ryandes...@macports.org>
Date: Sun, April 29, 2012 3:50 pm
To: j...@ayendesigns.com
Cc: macports-users@lists.macosforge.org
On Apr 29, 2012, at 17:39, j...@ayendesigns.com wrote:
> Well, let's back up a second. I installed mysql and mysql-server yesterday, and didn't make any manual changes, so should the my.cnf in the standard ports path (/opt/local/etc) only have 2 entries in it normally?
It's normal for /opt/local/etc/mysql5/my.cnf not to exist. MacPorts MySQL doesn't install it for you. If it exists, it's because you created it and put things into it. It can contain whatever you need or want in order to configure MySQL. As long as you do not set "socket=whatever" in a my.cnf file, it should use the default socket location I mentioned earlier.
/etc is another place where a my.cnf would be found.
More documentation at:
http://dev.mysql.com/doc/refman/5.1/en/option-files.html
> Is it a matter then of adding the path to the front of $PATH
$PATH has nothing to do with where MySQL looks for my.cnf or where it puts the socket file.
> or renaming the other instances to .old?
If you find other my.cnf files on your drive and you don't wish for them to be used, you can delete them or rename them as you like.
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
