On 30 Aug 2007, at 08:03, Juraj Lutter wrote:
> to whom it may concern and/or interest:
>
> I have made a patch allowing connection to "localhost" over tcp/ip,
> where mysql-proxy can sit on 127.0.0.1:3306 proxying to, for
> example, different host or zone.
>
> This may come handy, for example, when you need to migrate a
> webserver to different box but still retain "localhost" in user
> scripts.
>
> In my case it was very important, as I've moved MySQL server to one
> Solaris 10 zone and web server to another one and wanted to hide
> the change from customers.
>
> Patch against 5.1.21-beta is available at
> http://ftp.wilbury.sk/pub/mysql/mysql-5.1.21-beta-forcetcp-otis.patch
Hi Otis.
Thank you for the patch. I spent a while reviewing it and preparing
two complaints (1: "tcp" should be the value of the new variable, not
in the name, since we may not always use TCP. 2: the ACL system uses
"localhost", and it's confusing that "localhost"!="localhost" after
this change.)
Then, someone here told me of a parameter I've never noticed before:
"--protocol=" (in 4.1 and up) should get you the same behavior as
this patch for "--protocol=tcp", I think. Can you see a difference
that we should consider?
It looks to me like the behavior we'd like already exists, but it's
just not widely known.
- chad
--
Chad Miller, Software Developer chad@stripped
MySQL Inc., www.mysql.com
Orlando, Florida, USA 13-20z, UTC-0400
Office: +1 408 213 6740 sip:6740@stripped
(If it's not cyrptographically signed, it's not from Chad)
Attachment: [application/pgp-signature] This is a digitally signed message part PGP.sig
