database apps that ignore sockets? [was: Solution: mysqld fails to run, can't create/find mysql.sock]

Chuck Swiger cswiger at
Sun Jan 15 16:18:01 UTC 2012

On Jan 14, 2012, at 5:18 PM, Paul Beard wrote:
> Turns out some applications won't work if you move the socket if they are configured to access localhost. Seems like a misunderstanding of networking if you can specify a port number in a configuration file but the application looks to the filesystem for the socket. There is no way to specify a file location so it seems doomed to fail — as it did. 

Something looking for a network location specified as a host and port (ie, localhost:3306) is using a TCP socket.  Something looking for /tmp/mysqld.sock is using a UNIX domain socket.

Changing the path to the UNIX domain socket will have no effect upon the port used by the TCP socket, or vice versa.


More information about the freebsd-questions mailing list