AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20081030193947.68c12a7b@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<john.rogers@onstor.com>,<brian.stark@onstor.com>,<jonathan.goldick@onstor.com>,<ARoldan@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 30 Oct 2008 19:42:02 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: John Rogers <john.rogers@onstor.com>
Cc: Brian Stark <brian.stark@onstor.com>, Jonathan Goldick
 <jonathan.goldick@onstor.com>, Arnaldo Roldan <ARoldan@onstor.com>
Subject: dogfood problems
Message-ID: <20081030194202.293da4f7@ripper.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

John,

In regard to the mightydog problems, there's definitely some crapola
involving exim and RMC, and currently it's looking like I will
have to modify exim in order to put a stop to it.  While I'm in the
process of engineering that fix, which might take a couple of days, I
can add a little bandaid/stopgap to mightydog that will prevent exim and
RMC's problems from messing up the rest of the operation of the filer.
Let me know if you want me to do that.  It would involve adding a
couple of lines of code to the cfmond.sh daemon to monitor the number
of running exim processes and kill off ones that are stuck.

Let me know what you think.

Cheers,

a

