Stefan Beke wrote: >> If you perform a `ps aux` you will see what user dovecot is running as, >> that's the user whose class you want to check. > > [EMAIL PROTECTED] ~ $sudo ps waxu | grep dovecot > root 26251 0.0 0.2 620 912 ?? Ss 15Jan07 > 0:55.12/usr/local/sbin/dovecot > _dovecot 13219 0.0 0.3 560 1580 ?? S 8:02AM 0:00.11 pop3-login > _dovecot 3653 0.0 0.3 652 1584 ?? S 8:02AM 0:00.12 pop3-login > _dovecot 9416 0.0 0.3 540 1564 ?? S 8:02AM 0:00.11 imap-login > root 32241 0.0 0.2 592 1012 ?? S 8:02AM 0:00.09dovecot-auth > _dovecot 16174 0.0 0.3 576 1564 ?? S 8:12AM 0:00.11 pop3-login > _dovecot 19555 0.0 0.3 520 1592 ?? S 10:29AM 0:00.01 imap-login > _dovecot 13961 0.0 0.3 504 1564 ?? S 10:29AM 0:00.01 imap-login > ico 22226 0.0 0.1 448 504 p6 S+ 10:30AM 0:00.00 grep > dovecot > > [EMAIL PROTECTED] ~ $sudo lsof -p 26251 | wc -l > 38 > > Right now nobody is connected. I can imagine if someone connects and wants > to read bigger maildir through IMAP, it can be more than default 64.
Yep, it LOVES to chew fd's :-) > My daemon class is now on 512 files. Removed dovecot class. > I'll try this for a while. That's probably the less preferable option. The best way would be to leave the dovecot class, make sure the _dovecot user is allocated to that class (Nico's post will show you that) and then modify the limits for that class only - modifying the daemon class will affect all processes that come it. Dave
