* src/ejabberdctl.cfg.example: Explain that each connection uses

two or three ports (thanks to Max Loparyev)

SVN Revision: 1043

diff --git a/ChangeLog b/ChangeLog
index c4e8addf91ba107fd2ddffc727f2af4ee1e6333d..55884170ee3422baffd75a163121a9529c58eac0 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,8 @@
 2007-12-06  Badlop  <badlop@process-one.net>
 
+       * src/ejabberdctl.cfg.example: Explain that each connection uses
+       two or three ports (thanks to Max Loparyev)
+
        * src/configure: Regenerated
        * doc/dev.html: Likewise
        * doc/features.html: Likewise

diff --git a/src/ejabberdctl.cfg.example b/src/ejabberdctl.cfg.example
index ceceb725fc3f5f75a8c36184bed9f0be7b681bd8..af2206f5e05132dc5fd8608f692f176fbe52c5e1 100644 (file)
--- a/src/ejabberdctl.cfg.example
+++ b/src/ejabberdctl.cfg.example
@@ -27,9 +27,9 @@
 
 # ERL_MAX_PORTS: Maximum number of simultaneously open Erlang ports
 #
-# Erlang consumes one port for every connection, either from a client or from
-# another Jabber server. The option ERL_MAX_PORTS limits the number of
-# concurrent connections and can be specified when starting ejabberd.
+# ejabberd consumes two or three ports for every connection, either 
+# from a client or from another Jabber server. So take this into
+# account when setting this limit.
 #
 # Default: 1024
 # Maximum: 268435456