#30678: mysql5 should not read /etc/my.cnf -----------------------------------+---------------------------------------- Reporter: jeremyhu@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.1 Keywords: | Port: mysql5 -----------------------------------+---------------------------------------- Comment(by jeremyhu@…): Replying to [comment:12 ryandesign@…]:
Are you saying that the file /etc/my.cnf was not created by you but was provided by Apple on Mac OS X Snow Leopard Server?
Correct
If so I can see how that would cause this problem now. But I had also understood that [http://www.theregister.co.uk/2011/08/02/apple_dumps_mysql_from_mac_os_x_serv... Mac OS X Lion Server does not include MySQL anymore]. And of course Mac OS X client has never included MySQL. So I don't see how you're going to be able to migrate a Snow Leopard Server Apple MySQL setup to Lion Server anyway, without finding another way (like MacPorts) to install MySQL.
Lion includes MySQL for in-place upgrades from SL Server to Lion Server, but it is an older version. Erase installs of Lion Server do not have MySQL.
By "'claiming' /var/mysql" are you saying that MacPorts mysqld was creating its socket in that directory and keeping it open?
Yes
That should only have happened if MacPorts mysqld was started. And if you started MacPorts mysqld
I did not start it myself. It was started by launchd because I had the mysql5-server port installed (as part of install testing as mentioned above) but not configured.
that's a good indication that you're actually using it for something, and that perhaps Apple's migration script was right in not trying to interfere with it.
Unfortunately, I didn't realize that the launcdaemon was enabled by default as I never used it. -- Ticket URL: <https://trac.macports.org/ticket/30678#comment:13> MacPorts <http://www.macports.org/> Ports system for Mac OS