mirror of
https://github.com/processone/ejabberd.git
synced 2024-12-02 16:37:52 +01:00
* src/ejabberdctl.cfg.example: Explain that each connection uses
two or three ports (thanks to Max Loparyev) SVN Revision: 1043
This commit is contained in:
parent
dfa74082f8
commit
e79aa93d88
@ -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
|
||||
|
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user