Mercurial > dovecot > original-hg > dovecot-1.2

comparison dovecot-example.conf @ 4538:9d9e72374164 HEAD

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Fixes to login process handling, especially with login_process_per_connection=no. Removed login_max_logging_users setting since it was somewhat weird in how it worked. Added login_max_connections to replace it with login_process_per_connection=no, and with =yes its functionality is now within login_max_processes_count.
author Timo Sirainen <tss@iki.fi>
date Sun, 06 Aug 2006 23:05:32 +0300
parents 38f9daea3279
children c8177c854d65
comparison
equal deleted inserted replaced
4537:555c27e58cb1 4538:9d9e72374164
140 # login process be allowed to process multiple connections (no)? Yes is more 140 # login process be allowed to process multiple connections (no)? Yes is more
141 # secure, espcially with SSL/TLS enabled. No is faster since there's no need 141 # secure, espcially with SSL/TLS enabled. No is faster since there's no need
142 # to create processes all the time. 142 # to create processes all the time.
143 #login_process_per_connection = yes 143 #login_process_per_connection = yes
144 144
145 # Number of login processes to create. If login_process_per_connection is 145 # Number of login processes to keep for listening new connections.
146 # yes, this is the number of extra processes waiting for users to log in.
147 #login_processes_count = 3 146 #login_processes_count = 3
148 147
149 # Maximum number of extra login processes to create. The extra process count 148 # Maximum number of login processes to create. The listening process count
150 # usually stays at login_processes_count, but when multiple users start logging 149 # usually stays at login_processes_count, but when multiple users start logging
151 # in at the same time more extra processes are created. To prevent fork-bombing 150 # in at the same time more extra processes are created. To prevent fork-bombing
152 # we check only once in a second if new processes should be created - if all 151 # we check only once in a second if new processes should be created - if all
153 # of them are used at the time, we double their amount until limit set by this 152 # of them are used at the time, we double their amount until the limit set by
154 # setting is reached. This setting is used only if 153 # this setting is reached.
155 # login_process_per_connection is yes.
156 #login_max_processes_count = 128 154 #login_max_processes_count = 128
157 155
158 # Maximum number of connections allowed in login state. When this limit is 156 # Maximum number of connections allowed per each login process. This setting
159 # reached, the oldest connections are dropped. If login_process_per_connection 157 # is used only if login_process_per_connection=no. Once the limit is reached,
160 # is no, this is a per-process value, so the absolute maximum number of users 158 # the process notifies master so that it can create a new login process.
161 # logging in actually login_processes_count * max_logging_users. 159 # When counting the number of connections and used file descriptors, you
162 #login_max_logging_users = 256 160 # can use this table:
161 # Type Logged in SSL/TLS fds used connections used
162 # Client - - 1 1
163 # Client x - 0 0
164 # Client - x 3 2
165 # Client x x 2 1
166 # Proxy - - 2 2
167 # Proxy x - 2 1
168 # Proxy - x 4 3
169 # Proxy x x 3 2
170 # So in worst case scenario when you have n clients logging in, after STARTTLS
171 # they can use 3*n fds and cause the connection count to go 2 times higher
172 # than this limit. With proxying it can use 4*n fds and go 3 times higher.
173 #login_max_connections = 256
163 174
164 # Greeting message for clients. 175 # Greeting message for clients.
165 #login_greeting = Dovecot ready. 176 #login_greeting = Dovecot ready.
166 177
167 # Space-separated list of elements we want to log. The elements which have 178 # Space-separated list of elements we want to log. The elements which have