LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: Question

To: "tc lewis" <tim@xxxxxxxxxx>
Subject: Re: Question
Cc: "LVS Users Mailing List" <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
From: "Ted Pavlic" <tpavlic@xxxxxxxxxxx>
Date: Thu, 9 Sep 1999 14:37:37 -0400
I'm dong it on my LVS cluster with no trouble. The only problems I have are
with the file locking routines with RH6.0 and NFS -- but that's for a
completely different mailing list. :)

All the best --
Ted

----- Original Message -----
From: tc lewis <tim@xxxxxxxxxx>
To: Ilan Steemers <koed@xxxxxxxx>
Cc: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, September 09, 1999 2:11 PM
Subject: Re: Question


>
> or you could just use a disk shared via nfs or coda or something along
> those lines, if you don't want to spend the $ for fibre channel shared
> scsi devices or something along those lines.  =)
>
> or are you saying there would be issues/flaws in that?
>
> -tcl.
>
>
> On Thu, 9 Sep 1999, Ilan Steemers wrote:
>
> > Hi,
> >
> > How would you handle the data integrity across the servers? If mail
comes in it would have to be distributed among all the server, cause you
don't know where the user is going to pop. When a user pop's on a server,
you would have to delete those mail's on the other server as well. Load
balancing works fine for HTTP and FTP cause the data for those are pretyy
static. SMTP would be fine too, but POP? I doubt if that will work.
> > Oh wait, you could run those servers on a single high speed shared scsi
device. That way there's only one copy of the data. Those systems are rather
expensive, but it might work.
> >
> > Regards,
> >
> > Ilan Steemers
> >
> > hack@xxxxxxxxxxxxx wrote:
> >
> > > Hi folks,
> > >
> > > The ISP in the Netherlands that I'm currently working for, want me to
implement a scalable, high available (load balancing) mailserver. I have
been looking around and think the best way to do this is by having a daemon
listen to port 110 (POP3). This daemon will first ask the user's name and
then handle the traffic between the selected mailserver (the one with, for
example, the lowest traffic) and the user. I have a few questions, maybe you
folks can help me:
> > >
> > > - Since this daemon will be a SPOF (single point of failure), what do
I have to pay extra attention to?
> > >
> > > - Am I right when I think that there will be a maximum of 30,000 users
at the same time (since the daemon will have to open both sockets to the
user and the mailserver)? Can DNS be used as a solution for this?
> > >
> > > - Does anyone know of a daemon (or any software in general) that does
something similar to what I want to do or an URL with more info on this
subject (POP3 specific)?
> > >
> > > Any help is appreciated!
> > >
> > > Greetings, Norbert de Jonge
> > >
> > > ----------------------------------------------------------------
> > > Get your free email from AltaVista at http://altavista.iname.com
> > >
> > > ----------------------------------------------------------------------
> > > LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > > To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
> > > For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
> >
> >
> > ----------------------------------------------------------------------
> > LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
> > For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
> >
> >
>
>
> ----------------------------------------------------------------------
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
> For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx
>
>


----------------------------------------------------------------------
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
To unsubscribe, e-mail: lvs-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: lvs-users-help@xxxxxxxxxxxxxxxxxxxxxx


<Prev in Thread] Current Thread [Next in Thread>