[Dovecot] v2.x services documentation
If you've ever wanted to know everything about the service {} blocks, this should be quite helpful: http://wiki2.dovecot.org/Services
Well I've got some servers running 1.0 with dovecot, however, I make the installation of Dovecot 2.0 and would like to understand better the way it works.
It uses the files in / etc / dovecot / conf.d right?
Example: protocol pop3 protocol imap {{or is everything in / etc/dovecot/conf.d/10-master.conf?
Or the directory conf.d it is only for examples and everything is still done in dovecot.conf?
Thanks Lucas Possamai
2011/12/7 Timo Sirainen tss@iki.fi
If you've ever wanted to know everything about the service {} blocks, this should be quite helpful: http://wiki2.dovecot.org/Services
--
*Lucas Possamai*
http://www.facebook.com/profile.php?id=1362842471
taekwondo http://www.taeroque.com.br/
facebook http://www.facebook.com/profile.php?id=1362842471
vivaolinux http://www.vivaolinux.com.br/%7Epsyscrew
work http://www.ruguertech.com.br/
On Tue, 2011-12-20 at 10:26 -0200, drum.lucas@gmail.com wrote:
Well I've got some servers running 1.0 with dovecot, however, I make the installation of Dovecot 2.0 and would like to understand better the way it works.
It uses the files in / etc / dovecot / conf.d right?
Example: protocol pop3 protocol imap {{or is everything in / etc/dovecot/conf.d/10-master.conf?
Or the directory conf.d it is only for examples and everything is still done in dovecot.conf?
It still uses dovecot.conf just like before. It's just that the new included example dovecot.conf has an "!include conf.d/*.conf" line, and the example configuration is split in those files. So if you want to do it like the new example config does, you need to modify the conf.d/* files. (But all of this could have been done this way in v1.x already, so it's not really any different in that way.)
Le 7 déc. 2011 à 15:22, Timo Sirainen a écrit :
If you've ever wanted to know everything about the service {} blocks, this should be quite helpful: http://wiki2.dovecot.org/Services
Hello Timo,
I know, I'm quite late at reading the messages, and this is really a nice and useful one; thanks!
Up to now, I only had the opportunity to quickly read the wiki page, and have a small question; one may read:
process_min_avail Minimum number of processes that always should be available to accept more client connections. For service_limit=1 processes this decreases the latency for handling new connections. For service_limit!=1 processes it could be set to the number of CPU cores on the system to balance the load among them.
What's that service_limit setting?
TIA, Axel
On Sat, 2012-01-14 at 18:03 +0100, Axel Luttgens wrote:
Up to now, I only had the opportunity to quickly read the wiki page, and have a small question; one may read:
process_min_avail Minimum number of processes that always should be available to accept more client connections. For service_limit=1 processes this decreases the latency for handling new connections. For service_limit!=1 processes it could be set to the number of CPU cores on the system to balance the load among them.
What's that service_limit setting?
Thanks, fixed. Was supposed to be service_count.
participants (3)
-
Axel Luttgens
-
drum.lucas@gmail.com
-
Timo Sirainen