So guys, what do you suggest in theorethical level?
What would have to be done for multiple cyruses to work? Put a SQL DB in
backend?
|---------+------------------------------------->
| | Igor Brezac |
| | <[EMAIL PROTECTED]> |
| | Sent by: |
| | [EMAIL PROTECTED]|
| | rew.cmu.edu |
| | |
| | |
| | 2002.03.20 00:49 |
| | |
|---------+------------------------------------->
>--------------------------------------------------------------------------------------------------------------|
|
|
| To: Ken Murchison <[EMAIL PROTECTED]>
|
| cc: Chris Audley <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>, Earl R Shannon |
| <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
|
| Subject: Re: multiple cyruses via SAN
|
>--------------------------------------------------------------------------------------------------------------|
On Tue, 19 Mar 2002, Ken Murchison wrote:
>
>
> Chris Audley wrote:
> >
> > No, it will not work. A shared file system with unix lock semantics is
> > not enough, Berkeley DB will not work in this environment because it
> > uses shared memory. The system is single host bound.
>
> Yup. Good call. This could be worked around or just use non-BDB
> cyrusdb backends.
>
I do not see how this will work either. You can potentially get some
undesired results if you have several different imapd's on different
machines updating cyrusdb backends at the same time. Cyrus has no control
as to how will underlying SAN system update the file systems.
-Igor
