LMTPD sockets

2006-08-17 Thread David Korpiewski
This is building on my original discussion about simultaneous access: We are having a problem where two servers accessing the same SAN now give us a LMTPD error because they are stomping on each other's sockets (they share the same database on the SAN with the same socket directory). Is there

Re: LMTPD sockets

2006-08-17 Thread Scott Adkins
In a cluster (multi-machine) environment, such as Tru64 or Polyserve (on Linux), that problem is solved by the use of CDSL (a context-dependent symbolic link). You basically turn the file or directory into a CDSL and suddenly each machine in the cluster gets its own personal copy of it that is no

Re: LMTPD sockets

2006-08-17 Thread Ben Poliakoff
* David Korpiewski <[EMAIL PROTECTED]> [20060817 14:03]: > This is building on my original discussion about simultaneous access: > > We are having a problem where two servers accessing the same SAN now > give us a LMTPD error because they are stomping on each other's sockets > (they share the sa

Re: LMTPD sockets

2006-08-18 Thread David Korpiewski
Hi all, Yes, I did find this option in imapd.conf later on and this did "solve" the problem that I was trying. By changing the cyrus.conf file's socket location and also specifying lmtpsocket location in the imapd.conf, I was able to have two lmtpds running on two different servers using