First off, thank you to everyone who's chimed in with extremely helpful
suggestions in response to my previous message. Some of them have helped
performance, and others mysteriously haven't when I really thought they
would, but it's been very helpful for me in untying this knot. I've been
On Tue, Nov 10, 2009 at 11:51:42AM -0500, Michael Bacon wrote:
I have two questions regarding the Murder architecture. The first is just
a general annoyance at the way master starts up the mupdate processes. In
order to get master to fire off anything, you have to set prefork=1.
You can avoid the behavior in your second question by setting
mupdate_config: unified
in your proxies imapd.conf. That was a long standing issue with
murder in a large scale environment with cyrus 2.2.
On Tuesday 10 November 2009 @ 11:51, Michael Bacon wrote:
The second one is that the code
--On November 10, 2009 11:11:41 AM -0600 Gary Mills mi...@cc.umanitoba.ca
wrote:
I finally fixed that one, but it took a long time to find the reason.
I always had two copies of the mupdate master running, but one of them
did almost nothing...
# ps -fp $(pgrep mupdate)
UID
I saw this recommendation elsewhere, but I don't understand why one would
set mupdate_config: unified if I'm not, in fact, running a unified murder.
What's the gain here? We have dedicated front-end boxes and dedicated
back-end boxes. Is this just sort of a, yeah, it's not for that, but it
On Tuesday 10 November 2009 @ 12:37, Michael Bacon wrote:
I saw this recommendation elsewhere, but I don't understand why one
would set mupdate_config: unified if I'm not, in fact, running a
unified murder. What's the gain here? We have dedicated front-end
boxes and dedicated back-end boxes.
--On November 10, 2009 1:23:33 PM -0500 Brian Awood baw...@umich.edu
wrote:
Unfortunately it's not well documented, but the unified murder config
currently only works on a proxy host. Don't try to configure it on
a backend machine that has local mailboxes!!! Unless you want to
manually fix
