Sorry for the delay getting back about this, I meant to let people know
that the reason for this:
Also when this happens the cyrus master process kills all other active
imapd processes and restarts, is there a reason for this?
I've never heard of master doing that in response to ANY child
For Solaris SMF and Cyrus please use in your manifest for Cyrus IMAP:
property_group name='startd' type='framework'
propval name='ignore_error' type='astring' value='core,signal'/
/property_group
The imap service will not be restarted when an imap process is killed anymore.
Only
On 05 Jul 2010, at 10:56, Gavin Gray wrote:
Two of them have had imapd processes crash and leave core dumps in
the past couple of days. Looking at the core dumps with dbx we see
I'm not aware of bug fixes in those code paths. Given how little
those two code paths have in common, I'd suspect
Hi there,
We have three backend servers in our cyrus murder all like this:
name : Cyrus IMAPD
version: v2.3.15 2009/09/09 12:35:48
vendor : Project Cyrus
support-url: http://cyrusimap.web.cmu.edu
os : SunOS
os-version : 5.11
environment: Built w/Cyrus SASL 2.1.23
