On 03 Oct 2015, at 01:35, A. Schulze sca@andreasschulze.de wrote:
Am 02.10.2015 um 18:13 schrieb Timo Sirainen:
- Added imap-hibernate processes (see imap_hibernate_timeout setting). IDLEing IMAP connections can be hibernated, which saves memory.
using this settings, one thunderbird connected to an otherwise idle mailbox, I have there processes: 10312 ? Ss 0:00 /usr/sbin/dovecot -F 10316 ? S 0:00 \_ dovecot/anvil [10 connections] 10317 ? S 0:00 \_ dovecot/log 10319 ? S 0:00 \_ dovecot/config 10329 ? S 0:00 \_ dovecot/imap-hibernate [10 connections] 10350 ? S 0:00 \_ dovecot/imap-login [1 connections (1 TLS)] 10351 ? S 0:00 \_ dovecot/imap-login [1 connections (1 TLS)] 10366 ? S 0:00 \_ dovecot/imap-login [1 connections (1 TLS)] 10369 ? S 0:00 \_ dovecot/imap-login [1 connections (1 TLS)] 10372 ? S 0:00 \_ dovecot/imap-login [1 connections (1 TLS)] 10374 ? S 0:00 \_ dovecot/imap-login [1 connections (1 TLS)] 10377 ? S 0:00 \_ dovecot/imap-login [1 connections (1 TLS)] 10379 ? S 0:00 \_ dovecot/imap-login [1 connections (1 TLS)] 10382 ? S 0:01 \_ dovecot/imap-login [1 connections (1 TLS)] 10385 ? S 0:01 \_ dovecot/imap-login [1 connections (1 TLS)] 11744 ? S 0:00 \_ dovecot/ssl-params 11746 ? S 0:00 \_ dovecot/lmtp
is it OK that there are still 10 separte imap-login processes?
That's a separate issue. Switch to high-performance mode described in http://wiki2.dovecot.org/LoginProcess
are there concerns setting the mode for /var/run/dovecot/imap-master from 0600 to 0666?
Ideally avoid that. You can probably just do:
service imap { unix_listener imap-master { mode = 0600 user = vmail } }
and are there suggestions for imap_hibernate_timeout?
I'm interested in some good answers to this too :) Although in future it'll likely become automatic/dynamic.