Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<40428033.50C45209@dessent.net>
Date:	Sun, 29 Feb 2004 16:13:39 -0800
From:	Brian Dessent <brian AT dessent DOT net>
Organization:	My own little world...
MIME-Version:	1.0
To:	Cygwin mailing list <cygwin AT cygwin DOT com>
Subject:	Re: Crash of mysql under cygwin with g++ 3.3.1
References:	<15954380034 DOT 20040228015909 AT familiehaase DOT de> <Pine DOT LNX DOT 4 DOT 44 DOT 0402281333380 DOT 31254-100000 AT piz DOT ethz DOT ch> <115176853932 DOT 20040229120024 AT familiehaase DOT de> <4041C8DD DOT 9020903 AT inf DOT ethz DOT ch>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

Fabrice Marchal wrote:

> "cannot connect through /var/mysql/mysql.sock". The workaround is
> to use mysql_real_connect with host=127.0.0.1 because if I use
> "localhost" it turns to named pipes instead of using TCP. Any idea why it
> is that way?

Because Unix domain sockets are more efficient than TCP/IP ones.  So if
you specify 'localhost' as the host then there's a prety good chance
that a Unix socket is available, and so the client tries that.  It's an
optimization so that Unix sockets are used when talking to the
localhost, without the user having to explicitly configure it.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -