what exactly is the problem you experience when the maxchild value is reached? what do you mean by "overtime"?
cyrus imapd processes are designed to be long-lived, and to serve multiple clients before exiting. if your imap client users are few and their connections are long lived, then i would expect to see lots of processes existing for a long time. that's just normal behaviour - we really need a description of the problem you're experiencing after this point
the config andre provided might provide a start in tuning your setup better for your environment, please review it in conjunction with the cyrus.conf(5) man page
also keep in mind that common clients (e.g. thunderbird) will open many parallel connections, this is not unusual and not a problem unless it stresses your hardware
if in doubt, you can instruct cyrus to terminate any unused processes at any time by sending a SIGHUP to the master process. this won't affect any active client connections
cheers,
ellie
On Wed, Aug 30, 2017, at 08:56 PM, Paul van der Vlis wrote:
> Hello,
>
> I am testing Cyrus Imapd 2.5.10 from Debian stable. What I see is that
> the imapd processes become more and more overtime untill they reach the
> maxchild value, and then there is a problem. I see this with "ps aux |
> grep imapd".
>
> The server is only used by a few devices.
>
> Maybe I miss something in cleaning-up processes??
>
> With regards,
> Paul van der Vlis
>
>
> --
> Paul van der Vlis Linux systeembeheer Groningen
> https://www.vandervlis.nl/
>
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
