On Jan 15, 2012, at 8:43 AM, Paul Beard wrote: > Useful clarification but a UNIX domain socket sounds less like networking and > more like interprocess communication, i.e., something explicitly tied to a > single host.
Yes, that's right. > There is a "skip networking" option for MySQL that references the domain > socket for use by processes on the same host but doesn't accept connections > on port 3306. That also sounds familiar. > There's no indication that using localhost will default to a domain socket > which will explicitly be looked for in /tmp and if you put it anywhere else, > you must specify a hostname to access the TCP socket. You're confusing two things which are different. If you specify a path via "--socket=/tmp/mysqld.sock", you are describing a UNIX domain socket. While you can also specify "--host=localhost", that would be ignored because it it implicit. If you change where the socket lives in mysqld config or CLI options, you need to change where the clients look for the socket as well. If you specify a hostname and port via "--host=localhost --port=3306", then you are describing a TCP socket. There is no pathname involved. You could connect regardless of where mysqld is putting the socket. > I'll quote your definition in the bug report as it seems crystal clear. I would have said that the documentation seem clear as well: http://dev.mysql.com/doc/refman/5.5/en/multiple-server-clients.html http://dev.mysql.com/doc/refman/5.5/en/multiple-unix-servers.html ...but there's evidently some confusing aspect. Regards, -- -Chuck _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
