mirror of
https://github.com/processone/ejabberd.git
synced 2024-11-24 16:23:40 +01:00
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:
parent
9d84caebdb
commit
17607ecaa4
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user