[dovecot-cvs] dovecot dovecot-example.conf,1.194.2.16,1.194.2.17

[cras at dovecot.org]

Update of /var/lib/cvs/dovecot
In directory talvi:/tmp/cvs-serv23557

Modified Files:
      Tag: branch_1_0
	dovecot-example.conf 
Log Message:
Updated login_max_connections comment.



Index: dovecot-example.conf
===================================================================
RCS file: /var/lib/cvs/dovecot/dovecot-example.conf,v
retrieving revision 1.194.2.16
retrieving revision 1.194.2.17
diff -u -d -r1.194.2.16 -r1.194.2.17
--- dovecot-example.conf	6 Aug 2006 20:05:18 -0000	1.194.2.16
+++ dovecot-example.conf	10 Aug 2006 21:21:31 -0000	1.194.2.17
@@ -156,20 +156,8 @@
 # Maximum number of connections allowed per each login process. This setting
 # is used only if login_process_per_connection=no. Once the limit is reached,
 # the process notifies master so that it can create a new login process.
-# When counting the number of connections and used file descriptors, you
-# can use this table:
-#   Type     Logged in  SSL/TLS    fds used   connections used
-#   Client   -          -          1          1
-#   Client   x          -          0          0
-#   Client   -          x          3          2
-#   Client   x          x          2          1
-#   Proxy    -          -          2          2
-#   Proxy    x          -          2          1
-#   Proxy    -          x          4          3
-#   Proxy    x          x          3          2
-# So in worst case scenario when you have n clients logging in, after STARTTLS
-# they can use 3*n fds and cause the connection count to go 2 times higher
-# than this limit. With proxying it can use 4*n fds and go 3 times higher.
+# You should make sure that the process has at least
+# 16 + login_max_connections * 2 available file descriptors.
 #login_max_connections = 256
 
 # Greeting message for clients.