Am Dienstag 06 Juli 2010, 16:48:44 schrieb Gordon Messmer: > >> But apart from this, how could it happen that my configured limit of > >> maximum imap processes (MAXDAEMONS=200 and MAXPERIP=50) is not > >> respected? > How are you counting imapd processes?
Well, the easy way: $ ps aux [...] 2529 user 19 -1 17996 408 404 S 0 0.0 0:00.00 /usr/bin/imapd ... 32537 user 19 -1 17996 420 416 S 0 0.0 0:00.00 /usr/bin/imapd ... 32541 user 19 -1 17996 408 404 S 0 0.0 0:00.00 /usr/bin/imapd ... 32542 user 19 -1 17996 408 404 S 0 0.0 0:00.00 /usr/bin/imapd ... 32561 user 19 -1 17996 400 396 S 0 0.0 0:00.00 /usr/bin/imapd ... [...] $ ps aux | grep "/usr/bin/imapd /home/user" | wc -l 4095 (I replaced the real user account by "user" and the Maildir path by "..." to get all into one line.) Seems like couriertcpd can create new processes up to 4096. This matches the PAM-Limit for the root user (that started courier initially). When a further IMAP login is requested, the error is setuid: Resource temporarily unavailable
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
