Advertisement
Guest User

ejabberdctl.cfg

a guest
Jun 18th, 2010
429
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. #
  2. # In this file you can configure options that are passed by ejabberdctl
  3. # to the erlang runtime system when starting ejabberd
  4. #
  5.  
  6. # POLL: Kernel polling ([true|false])
  7. #
  8. # The kernel polling option requires support in the kernel.
  9. # Additionaly, you need to enable this feature while compiling Erlang.
  10. #
  11. # Default: true
  12. #
  13. POLL=true
  14.  
  15. # SMP: SMP support ([enable|auto|disable])
  16. #
  17. # Explanation in Erlang/OTP documentation:
  18. # enable: starts the Erlang runtime system with SMP support enabled.
  19. # This may fail if no runtime system with SMP support is available.
  20. # auto: starts the Erlang runtime system with SMP support enabled if it
  21. # is available and more than one logical processor are detected.
  22. # disable: starts a runtime system without SMP support.
  23. #
  24. # Default: auto
  25. #
  26. SMP=auto
  27.  
  28. # ERL_MAX_PORTS: Maximum number of simultaneously open Erlang ports
  29. #
  30. # ejabberd consumes two or three ports for every connection, either
  31. # from a client or from another Jabber server. So take this into
  32. # account when setting this limit.
  33. #
  34. # Default: 32000
  35. # Maximum: 268435456
  36. #
  37. ERL_MAX_PORTS=32000
  38.  
  39. # FIREWALL_WINDOW: Range of allowed ports to pass through a firewall
  40. #
  41. # If Ejabberd is configured to run in cluster, and a firewall is blocking ports,
  42. # it's possible to make Erlang use a defined range of port (instead of dynamic ports)
  43. # for node communication.
  44. #
  45. # Default: not defined
  46. # Example: 4200-4210
  47. #
  48. #FIREWALL_WINDOW=
  49.  
  50. # PROCESSES: Maximum number of Erlang processes
  51. #
  52. # Erlang consumes a lot of lightweight processes. If there is a lot of activity
  53. # on ejabberd so that the maximum number of proccesses is reached, people will
  54. # experiment greater latency times. As these processes are implemented in
  55. # Erlang, and therefore not related to the operating system processes, you do
  56. # not have to worry about allowing a huge number of them.
  57. #
  58. # Default: 250000
  59. # Maximum: 268435456
  60. #
  61. ERL_PROCESSES=250000
  62.  
  63. # ERL_MAX_ETS_TABLES: Maximum number of ETS and Mnesia tables
  64. #
  65. # The number of concurrent ETS and Mnesia tables is limited. When the limit is
  66. # reached, errors will appear in the logs:
  67. # ** Too many db tables **
  68. # You can safely increase this limit when starting ejabberd. It impacts memory
  69. # consumption but the difference will be quite small.
  70. #
  71. # Default: 1400
  72. #
  73. ERL_MAX_ETS_TABLES=1400
  74.  
  75. # The next variable allows to explicitly specify erlang node for ejabberd
  76. # It can be given in different formats:
  77. # ERLANG_NODE=ejabberd
  78. # Lets erlang add hostname to the node (ejabberd uses short name in this case)
  79. # ERLANG_NODE=ejabberd@hostname
  80. # Erlang uses node name as is (so make sure that hostname is a real
  81. # machine hostname or you'll not be able to control ejabberd)
  82. # ERLANG_NODE=ejabberd@hostname.domainname
  83. # The same as previous, but erlang will use long hostname
  84. # (see erl (1) manual for details)
  85. #
  86. ERLANG_NODE=ejabberd@`hostname -f`
Advertisement
Advertisement
Advertisement
RAW Paste Data Copied
Advertisement