On -10.01.-28163 20:59, Andreas Meyer wrote:
What is the best way to avoid this process_limit errors and configure dovecot the best way?
Which limits exactly your users' activities count against depends on what protocols they're using. (Example: N parallel IMAPS connections with (default setting) *individual* imap-login processes require the process_limit of the imap and imap-login services to be at least N, occupy 2xN in the client_limit of the auth service, and need the client_limit of the anvil service to be at least about N+100.) Your "fd limit (ulimit -n)" warning is about an adjustment you must make in the OS' config (the exact place/method, in turn, being distrib dependent). Note that a single client may well hold *several* IMAP(S) connections open in parallel, too. And that your server will need to have the CPU and RAM to run that many processes ...
How much overhead you're willing to provide beyond the current (or expected, or theoretical-max) needs of your users is up to you to decide, but since there's always the possibility of some malfunction or attack tearing into your limited ressources, you should *monitor* the usage, anyway.
Kind regards, J. Bern
*NEU* - NEC IT-Infrastruktur-Produkte im <http://www.linworks-shop.de/>: Server--Storage--Virtualisierung--Management SW--Passion for Performance Jochen Bern, Systemingenieur --- LINworks GmbH <http://www.LINworks.de/> Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt PGP (1024D/4096g) FP = D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C27 Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202 Unternehmenssitz Weiterstadt, Geschäftsführer Metin Dogan, Oliver Michel