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
This commit is contained in:
Pablo Polvorin 2010-02-03 15:04:56 +00:00 committed by Badlop
parent 9d84caebdb
commit 17607ecaa4
1 changed files with 2 additions and 2 deletions

View File

@ -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