Hi there,
Are there any known plans for the future of replication inside cyrus ?
There are a few things we dream of having, and that we consider
implementing. But if some of those do overlap with cyrus roadmap, maybe
we could help you by sharing the work ?
In no particular order:
1) Master-m
On Fri, 12 Aug 2011 11:16:30 +0200, Julien Coloos
wrote:
Hi there,
Are there any known plans for the future of replication inside cyrus ?
There are a few things we dream of having, and that we consider
implementing. But if some of those do overlap with cyrus roadmap, maybe
we could help
Hi there,
so I git pulled the cyrus-imapd master branch, built the code, installed it,
and ran cyrus-imapd with valgrind: "valgrind --show-reachable=yes --undef-
value-errors=yes --track-origins=yes --trace-children=yes --leak-check=full
/usr/cyrus/bin/cyrus-master"
I tested the mboxlist.c:mbo
Le 12/08/2011 13:37, Bron Gondwana a écrit :
On Fri, 12 Aug 2011 11:16:30 +0200, Julien Coloos
wrote:
1) Master-master replication
There are many difficulties to overcome for this feature, as well as
many ways to achieve it:
- 2-servers only, multi-master, ... ?
N servers - mesh, chain
We are pleased to announce the release of Cyrus IMAPd 2.4.11beta1.
You can download it from the snapshots directory:
http://www.cyrusimap.org/releases/snapshots/cyrus-imapd-2.4.11beta1.tar.gz
This is an beta release in the 2.4.x series.
This release fixes includes quite a lot of bugs, and
inclu
