Multi-thread cyrus delayed forking of imapd processes after connecting to master listener

Michael Hieb michael.hieb at
Wed May 24 00:50:12 EDT 2017

I set maxforkrate=100 to make to raise it well above a default. 100 a 
second is quite a lot and logs show I am no where near that many 

I am not sure if I can define the maxforkrate parameter so that it is 
unlimited (for testing) so I just set it at a number well above what I 
see the server trying to do.

I tried prefork and found it did not help the problem, most of the 
prefork sessions also had the wait condition.


On 05/24/2017 03:11 AM, Scott Lambert wrote:
> I may be completely missing the point and I don't know your environment.
> It looks like you may have designed in some delays if the server is
> pretty busy, especially during restart.
> On Fri, May 19, 2017 at 05:55:32PM +0800, Michael Hieb wrote:
>>> Here are the configuration details:
>>> imap cmd="imapd -C /etc/ "
>>> listen="" maxchild=-1 maxforkrate=100
>>> imaps cmd="imapd -C /etc/ -s "
>>> listen="" maxchild=-1 maxforkrate=100
> maxforkrate will limit you to 100 forks per second.  That's quite a lot
> but between bad guys and reconnects of clients after a restart, that may
> be limiting.  I'm not sure I understand maxforkrate without a maxchild
> limit.  That's probably a lack of imagination on my part.
> Maybe it would be good to prefork a few instances of each service?

More information about the Info-cyrus mailing list