From d809aafba0509117d763072f95a5170131c3bfb3 Mon Sep 17 00:00:00 2001 From: Evgeniy Khramtsov Date: Sat, 23 Jun 2018 20:01:21 +0300 Subject: [PATCH] Fix Erlang limits in ejabberdctl.cfg.example to reflect current situation --- ejabberdctl.cfg.example | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ejabberdctl.cfg.example b/ejabberdctl.cfg.example index d121aa824..0327da262 100644 --- a/ejabberdctl.cfg.example +++ b/ejabberdctl.cfg.example @@ -33,10 +33,10 @@ # from a client or from another Jabber server. So take this into # account when setting this limit. # -# Default: 32000 +# Default: 65536 (or 8196 on Windows) # Maximum: 268435456 # -#ERL_MAX_PORTS=32000 +#ERL_MAX_PORTS=65536 #. #' FIREWALL_WINDOW: Range of allowed ports to pass through a firewall @@ -85,10 +85,10 @@ # Erlang, and therefore not related to the operating system processes, you do # not have to worry about allowing a huge number of them. # -# Default: 250000 +# Default: 262144 # Maximum: 268435456 # -#ERL_PROCESSES=250000 +#ERL_PROCESSES=262144 #. #' ERL_MAX_ETS_TABLES: Maximum number of ETS and Mnesia tables @@ -99,9 +99,9 @@ # You can safely increase this limit when starting ejabberd. It impacts memory # consumption but the difference will be quite small. # -# Default: 1400 +# Default: 2053 # -#ERL_MAX_ETS_TABLES=1400 +#ERL_MAX_ETS_TABLES=2053 #. #' ERL_OPTIONS: Additional Erlang options -- 2.40.0