I need to add to my previous post -- You asked about using the SAME 
operating system socket as well as using separate addresses with the same 
port number (different IP sockets)

My answer to that is NOT ON YOUR LIFE. Think of the chaos. If one client 
tried to connect to an OS socket that 3 different servers were listening 
to... Which one gets the connection? Which one validates the client? If 
for some reason the client *were* able to validate against all three 
servers at the same time, how could it sort out the 3 different responses 
to a query?

NO each server must have it's own socket. It doesn't matter if we are 
discussing "IP sockets" or "OS sockets" the answer is still the same.

Sorry for the previous oversight,

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine

"Sanjeev Sagar" <[EMAIL PROTECTED]> wrote on 09/08/2004 
05:04:38 PM:

> 
> Hello All,
> 
> MySQL : Standar Binary 4.0.20
> O/S : Red Hat Linux release 9 (Shrike)
> Linux  2.4.20-31.9smp #1 SMP Tue Apr 13 17:40:10 EDT 2004 i686 i686 
> i386 GNU/Linux
> 
> I already have setup of Three Multiple MySQL servers listening on 
> different ports and sockets on same machine
> 
> Option File:
> 
> [mysqld1]
> server-id =1
> port=3306
> socket=/tmp/mysql.sock
> datadir=data1
> 
> [mysqld2]
> server-id=2
> port=3307
> socket=/tmp/mysql.sock2
> datadir=data2
> 
> [mysqld3]
> server-id=3
> port=3308
> socket=/tmp/mysql.sock3
> datadir=data3
> 
> All three servers started with no problem. Question is if I don't 
> want to use different ports or scokets, can I use the different I.P.
> Addresses on same machine for three servers with same default port or 
socket.
> 
> /etc/hosts file
> ===============
> 
> 127.0.0.100  s1
> 127.0.0.101  s2
> 127.0.0.102   s3
> 
> 
> Can I start three servers on  same port (3306), same socket 
> (/tmp/mysql.sock) on same machine by using above IP addresses? If 
> yes then HOW?
> 
> Can I use the replication in b/w them? keeping datadir and log-bin 
> directory differtent is not a problem.
> 
> Appreciate it.
> 

Reply via email to