|
yeah, i wasn't really worried about the queueing as much as when qmail
grabs messages out of the queue to send/deliver. if both try to do it at
the same time, what happens? qmail's pretty smart, but i don't know what
kind of locking mechanisms it has for stuff like that. that could get
shaky. maybe i'm just not looking at it right.
-tcl.
On Thu, 20 Apr 2000, Jeremy Hansen wrote:
>
> If the qmail queue is on the same filesystem, I believe it should be ok
> since qmail writes it's queue files as the name of the inode on the
> filesystem. This should keep things unique, I think.
>
> -jeremy
>
> >
> > i've never tried it with coda, but i've used qmail+lvs successfully. if
> > you use tcpserver, there's some flag to turn off ident lookups. use that,
> > or you'll get major bad performance.
> >
> > you're going to share the queue and have both qmails running at the same
> > time? hmm, that could get messy. i'm not sure if qmail handles that
> > safely or not. it indeed might. if you're just going to use it for
> > failover safety, that shouldn't be an issue, but both going at the same
> > time with a shared queue dir? hum...
> >
> > -tcl.
> >
> >
> > On Thu, 20 Apr 2000, Madhav wrote:
> >
> > > Hi all,
> > >
> > > We have set up a LVS cluster with heartbeat, mon and coda(2 routers+2 real
> > > servers) for telnet,ftp and http services. I am planning to implement the
> > > mail service also in this setup.
> > >
> > > Now I have installed qmail in one real server and it is working fine. I am
> > > planning to install qmail under coda(usually qmail directory will be under
> > > /var/qmail) so that I can have replication of mail data(with coda) and
> > > also
> > > masking of the failed mail server(with mon). I would like to know whether
> > > anyone tried this earlier and if not can anyone foresee any problems with
> > > this setup(like both the mail servers trying at the same time to send
> > > mails
> > > from the same mail queue)?.
> > > Any suggestions or ideas will be appreciated.
> > >
> > > Thanks,
> > > Madhav
> > >
> > >
> > >
> > >
> >
> >
> >
>
> --
>
> http://www.xxedgexx.com | jeremy@xxxxxxxxxxxx
> ---------------------------------------------
>
>
>
>
|
