I'm using Cyrus replication. After several tests, it seems that the
single instance store facility is not replicated. I mean, the same
message sent to several recipient is stored once on the master, but
stored several times on the slave. Is there a special thing to do to
activate single
On Thu, 2007-03-01 at 16:41 -0600, Blake Hudson wrote:
Actually it's still happening :( I read in the archives that the only
way to actually avoid the locking in deliver.db is to also disable
sieve, is that true?
So, I'm willing to recompile cyrus and comment the calls to
dupicate_check()
I'm using Cyrus replication. After several tests, it seems that the
single instance store facility is not replicated. I mean, the same
message sent to several recipient is stored once on the master, but
stored several times on the slave. Is there a special thing to do to
activate single
Hy all again!
I get more information.
In copying from my slave 2.3.8 the sync_client and sync_server
files to the master in 2.3.7 I am now able to run sync_client
-v -m user.toto2 on my master it works!
I think there is an incompatibility between the two modules
but i'm absolutely unable to
Hy all again!
I get more information.
In copying from my slave 2.3.8 the sync_client and sync_server
files to the master in 2.3.7 I am now able to run sync_client
-v -m user.toto2 on my master it works!
I think there is an incompatibility between the two modules
but i'm absolutely unable to
On Fri, 2 Mar 2007, Andre Nathan wrote:
On Thu, 2007-03-01 at 16:41 -0600, Blake Hudson wrote:
Actually it's still happening :( I read in the archives that the only
way to actually avoid the locking in deliver.db is to also disable
sieve, is that true?
So, I'm willing to recompile cyrus and
On Fri, 2007-03-02 at 12:59 -0800, Andrew Morgan wrote:
You'll lose the ability to effectively use vacation/out-of-office
messages. The vacation system uses deliver.db to determine which person
has already received the vacation message, to prevent multiple messages
from being sent.
But
On Fri, 2 Mar 2007, Andre Nathan wrote:
On Fri, 2007-03-02 at 09:21 -0300, Andre Nathan wrote:
Is there a cyrus version where specifying duplicatesuppression: 0
actually prevents the duplicate check and thus the database locking
issues I could upgrade to a newer version too, no problem.
I
On Fri, 2007-03-02 at 17:07 -0800, Andrew Morgan wrote:
I doubt this is the problem you are seeing. It sounds to me like you may
be hitting the limits of your storage system. I would be fascinated to
see the output of the command iostat -x sdb 5 (where 'sdb' is the device
you have cyrus
You can view the load average and process counts for these servers at:
https://secure.onid.oregonstate.edu/cacti/graph_view.php?action=treetree_id=4
OT, but I found this interesting... I wonder when school starts and ends and
when holidays are :)
see the output of the command iostat -x sdb 5 (where 'sdb' is the device
you have cyrus on) on your system. Even if you aren't saturating your
Gigabit Ethernet link to the ATA-over-Ethernet storage, you may be
exceeding the number I/O operations per second.
I thought ATA-over-Ethernet had
After running iostat on my cyrus partition (both config and mail spool
are
kept on a SAN), I'm wondering if I should separate them out as well.
This
sounds related to the new metapartition and metapartition_files options
that were added in v2.3.x.
Does anyone have any recommendations or
12 matches
Mail list logo
