--- [EMAIL PROTECTED] wrote ---
> In this case it might be easier for you to just modify the MySQL
> source to disable looking for the socket, and treat localhost as
> 127.0.0.1.
>
> --Pete
Pete,
I've considered that (and I'm going to try it on a development box).
Unfortunately the target of thi
In this case it might be easier for you to just modify the MySQL
source to disable looking for the socket, and treat localhost as
127.0.0.1.
--Pete
On Fri, Jan 30, 2004 at 06:33:22AM -0800, [EMAIL PROTECTED] wrote:
> --- [EMAIL PROTECTED] wrote ---
> > i've never set up tunnels and such, but are
--- [EMAIL PROTECTED] wrote ---
> i've never set up tunnels and such, but are you sure that your ssh
> tunnel is also listening on localhost (i.e. 127.0.0.1)? i once had a
> problem like that with my apache, and it turned out that it only
> listened on 'real' IPs
Yeah, the tunnels work perf
i've never set up tunnels and such, but are you sure that your ssh
tunnel is also listening on localhost (i.e. 127.0.0.1)? i once had a
problem like that with my apache, and it turned out that it only
listened on 'real' IPs
cheers and good luck,
M.
[EMAIL PROTECTED] wrote:
Greetings,
Th
Greetings,
This is a complicated one (at least to explain), but it never hurts to
ask, right?
While the problem lies mostly in PHP scripts, this also happens with the
standalone MySQL client (v4.0.15 I believe).
Normally the client (PHP and command-line) tries to use the local socket
if the mysq
