[MacPorts] #30678: mysql5 should not read /etc/my.cnf
MacPorts
noreply at macports.org
Wed Aug 10 19:54:13 PDT 2011
#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 ryandesign@…):
It sounds like on your system you had a file /etc/my.cnf that specified
that the socket should live in /var/mysql/mysql.sock, and so MacPorts
MySQL honored that request, as would any other distribution of MySQL. If
you had not had that file with those contents MacPorts MySQL would have
used its default socket at /opt/local/var/run/mysql5/mysqld.sock.
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? 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_server/
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.
By "'claiming' /var/mysql" are you saying that MacPorts mysqld was
creating its socket in that directory and keeping it open? That should
only have happened if MacPorts mysqld was started. And if you started
MacPorts mysqld, 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.
--
Ticket URL: <https://trac.macports.org/ticket/30678#comment:12>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list