On 09.04.2006 01:03 (+0100), Eric Braswell wrote:
> Does that make sense? Did I misunderstand?
That's exactly what I'm doing right now. In my test network:
MySQL 4.0 -> 192.168.0.32 (mysql4.myhost)
MySQL 5.0 -> 192.168.0.33 (mysql5.myhost)
But what I wanted to do is:
MySQL 4.0 -> 192.168.0.32 and 127.0.0.1
MySQL 5.0 -> 192.168.0.33
to a) keep both servers on different IPs with DNS names and b) let
system applications connect via the localhost interface which lets me
put additional security into it by only allowing access from localhost
for these applications, while all other users may connect from
everywhere. And of course, connecting to 127.0.0.1 is the obvious way in
a small webhosting environment, but that's not so important, I can tell
my users to change their database connection to the new name (mysql4)
when I migrate to the new server.
Or is there another way to only allow certain users to connect from
localhost?
As I think about it, a local TCP forwarder would accept connections on
localhost, but MySQL won't see that, so this wouldn't work anyway.
--
Yves Goergen "LonelyPixel" <[EMAIL PROTECTED]>
"This message represents the official view of the voices in my head."
http://newsboard.unclassified.de - Unclassified NewsBoard Forum
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
