On Tue, 13 Sep 2016, at 10:44, ellie timoney via Info-cyrus wrote: > Note that it talks about the process being used for new connections. > Each imapd process serves one connection at a time (so if you have 50 > client connections, you will have 50 imapd processes to serve them, plus > whatever you have preforked ready to serve new connections). When one > of these connections disconnects, the imapd process that was serving > that connection goes back into the pool, ready to serve a new incoming > connection -- unless it has already served $uses connections, in which > case it exits, and master spawns a new one instead if necessary. > > So you can see how, if you have mostly long-lived connections, each > imapd's count of how many connections it has served would grow very very > slowly -- many may not ever reach their limit, because you end up > needing to reboot the server (OS security updates, data centre works, > etc) before that occurs. If you look in /var/lib/imap/proc/* you should see one file for each process id, which tells you who is connected to that process, and which folder they have selected (if any). This is quite useful for tracking down if there's a single user causing issues. Bron. -- Bron Gondwana brong@xxxxxxxxxxx ---- 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
