Multi-thread cyrus delayed forking of imapd processes after connecting to master listener
Scott Lambert
lambert at lambertfam.org
Tue May 23 15:11:38 EDT 2017
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/imapd.domain1.com.conf "
> > listen="192.168.171.4:imap" maxchild=-1 maxforkrate=100
> >
> > imaps cmd="imapd -C /etc/imapd.domain1.com.conf -s "
> > listen="192.168.171.4:imaps" 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?
--
Scott Lambert KC5MLE Unix SysAdmin
lambert at lambertfam.org
More information about the Info-cyrus
mailing list