Date: Sun, 15 Jan 2012 08:43:13 -0800 From: Paul Beard <paulbeard@gmail.com> Cc: FreeBSD-questions <questions@Freebsd.org> Subject: Re: database apps that ignore sockets? [was: Solution: mysqld fails to run, can't create/find mysql.sock] Message-ID: <3720E228-67EE-4F44-B828-AFA0125D2A54@gmail.com> In-Reply-To: <3D14230E-7E8A-4E35-8161-F5F9CB74C83C@mac.com> References: <0F82362E-2694-4EBC-B019-DE2F2C160D45@gmail.com> <7325D262-C6EB-42DB-870D-D3E2FAC9D0C1@mac.com> <1954AA20-BE6F-4F04-A770-49ECFA405B5D@gmail.com> <3D14230E-7E8A-4E35-8161-F5F9CB74C83C@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 15, 2012, at 8:17 AM, Chuck Swiger wrote: > 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. > 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. 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. 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. I'll quote your definition in the bug report as it seems crystal clear. -- Paul Beard Are you trying to win an argument or solve a problem?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3720E228-67EE-4F44-B828-AFA0125D2A54>