Date: Sun, 15 Jan 2012 08:17:58 -0800 From: Chuck Swiger <cswiger@mac.com> To: 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: <3D14230E-7E8A-4E35-8161-F5F9CB74C83C@mac.com> In-Reply-To: <1954AA20-BE6F-4F04-A770-49ECFA405B5D@gmail.com> References: <0F82362E-2694-4EBC-B019-DE2F2C160D45@gmail.com> <7325D262-C6EB-42DB-870D-D3E2FAC9D0C1@mac.com> <1954AA20-BE6F-4F04-A770-49ECFA405B5D@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Regards, -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D14230E-7E8A-4E35-8161-F5F9CB74C83C>