mirror of
https://github.com/processone/ejabberd.git
synced 2024-11-24 16:23:40 +01:00
204 lines
6.2 KiB
Plaintext
204 lines
6.2 KiB
Plaintext
#
|
|
# In this file you can configure options that are passed by ejabberdctl
|
|
# to the erlang runtime system when starting ejabberd
|
|
#
|
|
|
|
#' POLL: Kernel polling ([true|false])
|
|
#
|
|
# The kernel polling option requires support in the kernel.
|
|
# Additionally, you need to enable this feature while compiling Erlang.
|
|
#
|
|
# Default: true
|
|
#
|
|
#POLL=true
|
|
|
|
#.
|
|
#' ERL_MAX_PORTS: Maximum number of simultaneously open Erlang ports
|
|
#
|
|
# ejabberd consumes two or three ports for every connection, either
|
|
# from a client or from another XMPP server. So take this into
|
|
# account when setting this limit.
|
|
#
|
|
# Default: 65536 (or 8196 on Windows)
|
|
# Maximum: 268435456
|
|
#
|
|
#ERL_MAX_PORTS=65536
|
|
|
|
#.
|
|
#' FIREWALL_WINDOW: Range of allowed ports to pass through a firewall
|
|
#
|
|
# If ejabberd is configured to run in cluster, and a firewall is blocking ports,
|
|
# it's possible to make Erlang use a defined range of port (instead of dynamic
|
|
# ports) for node communication.
|
|
#
|
|
# Default: not defined
|
|
# Example: 4200-4210
|
|
#
|
|
#FIREWALL_WINDOW=
|
|
|
|
#.
|
|
#' INET_DIST_INTERFACE: IP address where this Erlang node listens other nodes
|
|
#
|
|
# This communication is used by ejabberdctl command line tool,
|
|
# and in a cluster of several ejabberd nodes.
|
|
#
|
|
# Default: 0.0.0.0
|
|
#
|
|
#INET_DIST_INTERFACE=127.0.0.1
|
|
|
|
#.
|
|
#' ERL_DIST_PORT: Port number for Erlang distribution
|
|
#
|
|
# For Erlang distribution, clustering and ejabberdctl usage, the
|
|
# Erlang VM listens in a random TCP port number, and the Erlang Port
|
|
# Mapper Daemon (EPMD) is spawned and used to determine this port
|
|
# number.
|
|
#
|
|
# ERL_DIST_PORT can define this port number. In that case, EPMD is
|
|
# not spawned during ejabberd startup, and ERL_EPMD_ADDRESS is
|
|
# ignored. ERL_DIST_PORT must be set to the same port number during
|
|
# ejabberd startup and when calling ejabberdctl. This feature
|
|
# requires at least Erlang/OTP 23.1.
|
|
#
|
|
# Default: not defined
|
|
#
|
|
#ERL_DIST_PORT=5210
|
|
|
|
#.
|
|
#' ERL_EPMD_ADDRESS: IP addresses where EPMD listens for connections
|
|
#
|
|
# This environment variable may be set to a comma-separated
|
|
# list of IP addresses, in which case the EPMD daemon
|
|
# will listen only on the specified address(es) and on the
|
|
# loopback address (which is implicitly added to the list if it
|
|
# has not been specified). The default behaviour is to listen on
|
|
# all available IP addresses.
|
|
#
|
|
# Default: 0.0.0.0
|
|
#
|
|
#ERL_EPMD_ADDRESS=127.0.0.1
|
|
|
|
#.
|
|
#' 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
|
|
# experience greater latency times. As these processes are implemented in
|
|
# Erlang, and therefore not related to the operating system processes, you do
|
|
# not have to worry about allowing a huge number of them.
|
|
#
|
|
# Default: 262144
|
|
# Maximum: 268435456
|
|
#
|
|
#ERL_PROCESSES=262144
|
|
|
|
#.
|
|
#' ERL_MAX_ETS_TABLES: Maximum number of ETS and Mnesia tables
|
|
#
|
|
# The number of concurrent ETS and Mnesia tables is limited. When the limit is
|
|
# reached, errors will appear in the logs:
|
|
# ** Too many db tables **
|
|
# You can safely increase this limit when starting ejabberd. It impacts memory
|
|
# consumption but the difference will be quite small.
|
|
#
|
|
# Default: 2053
|
|
#
|
|
#ERL_MAX_ETS_TABLES=2053
|
|
|
|
#.
|
|
#' ERL_OPTIONS: Additional Erlang options
|
|
#
|
|
# The next variable allows to specify additional options passed to
|
|
# all commands using erlang interpreter. This applies to starting
|
|
# ejabberd server itself but also auxiliary commands like for example
|
|
# starting debug shell. See erl(1) for list of commands that can be
|
|
# used here.
|
|
#
|
|
# It might be useful to add "-pa /usr/local/lib/ejabberd/ebin" if you
|
|
# want to add local modules in this path.
|
|
#
|
|
# Default: ""
|
|
#
|
|
#ERL_OPTIONS=""
|
|
|
|
#.
|
|
#' EJABBERD_OPTS: Additional Erlang options to start ejabberd
|
|
#
|
|
# The next variable allows to specify additional options passed to erlang while
|
|
# starting ejabberd. Some useful options are -noshell, -detached, -heart. When
|
|
# ejabberd is started from an init.d script options -noshell and -detached are
|
|
# added implicitly. See erl(1) for more info.
|
|
#
|
|
# For example you can use value "-heart -env HEART_BEAT_TIMEOUT 120 -env ERL_CRASH_DUMP_SECONDS 60"
|
|
#
|
|
# Default: ""
|
|
#
|
|
#EJABBERD_OPTS=""
|
|
|
|
#.
|
|
#' ERLANG_NODE: Erlang node name
|
|
#
|
|
# The next variable allows to explicitly specify erlang node for ejabberd
|
|
# It can be given in different formats:
|
|
# ERLANG_NODE=ejabberd
|
|
# Lets erlang add hostname to the node (ejabberd uses short name in this case)
|
|
# ERLANG_NODE=ejabberd@hostname
|
|
# Erlang uses node name as is (so make sure that hostname is a real
|
|
# machine hostname or you'll not be able to control ejabberd)
|
|
# ERLANG_NODE=ejabberd@hostname.domainname
|
|
# The same as previous, but erlang will use long hostname
|
|
# (see erl (1) manual for details)
|
|
#
|
|
# Default: ejabberd@localhost
|
|
#
|
|
#ERLANG_NODE=ejabberd@localhost
|
|
|
|
#.
|
|
#' EJABBERD_PID_PATH: ejabberd PID file
|
|
#
|
|
# Indicate the full path to the ejabberd Process identifier (PID) file.
|
|
# If this variable is defined, ejabberd writes the PID file when starts,
|
|
# and deletes it when stops.
|
|
# Remember to create the directory and grant write permission to ejabberd.
|
|
#
|
|
# Default: don't write PID file
|
|
#
|
|
#EJABBERD_PID_PATH=/var/run/ejabberd/ejabberd.pid
|
|
|
|
#.
|
|
#' EJABBERD_CONFIG_PATH: ejabberd configuration file
|
|
#
|
|
# Specify the full path to the ejabberd configuration file. If the file name has
|
|
# yml or yaml extension, it is parsed as a YAML file; otherwise, Erlang syntax is
|
|
# expected.
|
|
#
|
|
# Default: $ETC_DIR/ejabberd.yml
|
|
#
|
|
#EJABBERD_CONFIG_PATH=/etc/ejabberd/ejabberd.yml
|
|
|
|
#.
|
|
#' CONTRIB_MODULES_PATH: contributed ejabberd modules path
|
|
#
|
|
# Specify the full path to the contributed ejabberd modules. If the path is not
|
|
# defined, ejabberd will use ~/.ejabberd-modules in home of user running ejabberd.
|
|
#
|
|
# Default: $HOME/.ejabberd-modules
|
|
#
|
|
#CONTRIB_MODULES_PATH=/opt/ejabberd-modules
|
|
|
|
#.
|
|
#' CONTRIB_MODULES_CONF_DIR: configuration directory for contributed modules
|
|
#
|
|
# Specify the full path to the configuration directory for contributed ejabberd
|
|
# modules. In order to configure a module named mod_foo, a mod_foo.yml file can
|
|
# be created in this directory. This file will then be used instead of the
|
|
# default configuration file provided with the module.
|
|
#
|
|
# Default: $CONTRIB_MODULES_PATH/conf
|
|
#
|
|
#CONTRIB_MODULES_CONF_DIR=/etc/ejabberd/modules
|
|
|
|
#.
|
|
#'
|
|
# vim: foldmarker=#',#. foldmethod=marker:
|