>> 2) Several people on this list have confirmed that they are running
>> cyrus-imapd clusters on shared storage (SAN) which works fine with a
>> cluster filesystem. That tells me that shared access to cyrus
>> databases
>> works fine as long as the filesystem used provides proper
>> locking, which
On 2006-11-16 at 23:55 +0100, Phil Pennock wrote:
> Hopefully the last post on this topic for a while.
List owners/moderators: please indicate if these posts are undesired, in
which case I apologise for the intrusion. In that case, please indicate
if a last post with details of a new mailing-list
All,
> -Original Message-
> From: Janne Peltonen [mailto:[EMAIL PROTECTED]
> On Thu, Nov 23, 2006 at 08:42:16AM +0100, Simon Matter wrote:
> [...]
> > 2) Several people on this list have confirmed that they are running
> > cyrus-imapd clusters on shared storage (SAN) which works fine wit
> -Original Message-
> From: Simon Matter [mailto:[EMAIL PROTECTED]
> Hi Sarah,
>
> I'm really confused now.
>
> 1) You are talking about NAS as a possible solution and I
> don't know how
> that should work if NFS doesn't work. Until now I thought a
> NAS device is
> an embedded fil
>
> Greetings.
>
> We had a storage failure recently. A user's data were corrupted. The
> user client keeps terminated abnormally.Below are the error messages.I
> also noticed two .NEW files created in the user's INBOX. Can anybody
> gave me any suggestion?
Did you try to reconstruct the mailbox i
I'm having a slight problem understanding the cyrus docs[0] regarding
frontend to backend authentication for LMTP over TCP. all cyri are
2.2.13.
# backend imapd.log:
Nov 23 17:55:02 backend lmtp[21449]: accepted connection
Nov 23 17:55:02 backend lmtp[21449]: connection from frontend.example.org
Rudy Gevaert wrote:
>
> Did you restart saslauthd?
Yep, forgot to mention that.
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Greetings.
We had a storage failure recently. A user's data were corrupted. The
user client keeps terminated abnormally.Below are the error messages.I
also noticed two .NEW files created in the user's INBOX. Can anybody
gave me any suggestion?
Nov 23 08:58:14 cms3 imap[19511]: seen_db: user
On 11/23/06, Janne Peltonen <[EMAIL PROTECTED]> wrote:
You're completely correct, this is the kind of system I'm building and
others have had in production use (see the thread on clusters, GFS and
HA, for instance - begins at
http://www.mail-archive.com/info-cyrus@lists.andrew.cmu.edu/msg30675.ht
On Wed, 22 Nov 2006 09:47:46 -0600 Rich Graves <[EMAIL PROTECTED]> wrote:
> Phil Chambers wrote:
> > Rename the account from user.account to user.account-pending, keeping the
> > same
> > partition so that the rename is quick. Create a new account for
> > user.account
> > and put your single
Timo Veith wrote:
Rudy Gevaert wrote:
Some time ago we had some problems with sasl. When to many users are
connecting sasl starts blocking because it hasn't enough entropy.
Recompile sasl so it uses /dev/urandom instead of /dev/random.
Hello Rudy,
thank you for your tip. I recompiled cyrus-s
Rudy Gevaert wrote:
> Some time ago we had some problems with sasl. When to many users are
> connecting sasl starts blocking because it hasn't enough entropy.
> Recompile sasl so it uses /dev/urandom instead of /dev/random.
Hello Rudy,
thank you for your tip. I recompiled cyrus-sasl to use /dev/
Hi all,
just to comment on one isolated point:
On Thu, Nov 23, 2006 at 08:42:16AM +0100, Simon Matter wrote:
[...]
> 2) Several people on this list have confirmed that they are running
> cyrus-imapd clusters on shared storage (SAN) which works fine with a
> cluster filesystem. That tells me that
13 matches
Mail list logo
