From 17607ecaa4a2fab779476d74d5d68452441e10b0 Mon Sep 17 00:00:00 2001 From: Pablo Polvorin Date: Wed, 3 Feb 2010 15:04:56 +0000 Subject: [PATCH] Bug Fix: The value of max # of erlang process specified in ejabberdctl.cfg was not used. It was called PROCESSES in the .cfg file, and ERL_PROCESSES in the script. The latter is the correct, to be coherent with ERL_MAX_PORTS and ERL_MAX_ETS_TABLES. SVN Revision: 2959 --- src/ejabberdctl.cfg.example | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/ejabberdctl.cfg.example b/src/ejabberdctl.cfg.example index 1ba413fe2..4a3db1c8b 100644 --- a/src/ejabberdctl.cfg.example +++ b/src/ejabberdctl.cfg.example @@ -51,7 +51,7 @@ #FIREWALL_WINDOW= #. -#' PROCESSES: Maximum number of Erlang processes +#' ERL_PROCESSES: Maximum number of Erlang processes # # Erlang consumes a lot of lightweight processes. If there is a lot of activity # on ejabberd so that the maximum number of processes is reached, people will @@ -62,7 +62,7 @@ # Default: 250000 # Maximum: 268435456 # -#PROCESSES=250000 +#ERL_PROCESSES=250000 #. #' ERL_MAX_ETS_TABLES: Maximum number of ETS and Mnesia tables