From d7fbad6fa16c6d2cc9f9032beeda9205ce02dfcd Mon Sep 17 00:00:00 2001 From: Badlop Date: Thu, 18 Feb 2010 22:13:28 +0100 Subject: [PATCH] Recompile guide.html --- doc/guide.html | 30 ++++++++++++++++++++++++++++-- 1 file changed, 28 insertions(+), 2 deletions(-) diff --git a/doc/guide.html b/doc/guide.html index 99ae6409a..dfe7e2545 100644 --- a/doc/guide.html +++ b/doc/guide.html @@ -742,7 +742,15 @@ an incoming POST request can be configured with the global option The option can be defined in ejabberd.cfg, expressing the time in seconds: {http_poll_timeout, 300}.

{max_fsm_queue, Size}
-This option specifies the maximum number of elements in the queue of the FSM. +This option specifies the maximum number of elements in the queue of the FSM +(Finite State Machine). +Roughly speaking, each message in such queues represents one XML +stanza queued to be sent into its relevant outgoing stream. If queue size +reaches the limit (because, for example, the receiver of stanzas is too slow), +the FSM and the corresponding connection (if any) will be terminated +and error message will be logged. +The reasonable value for this option depends on your hardware configuration. +However, there is no much sense to set the size above 1000 elements. This option can be specified for ejabberd_service and ejabberd_c2s listeners, or also globally for ejabberd_s2s_out. @@ -828,7 +836,15 @@ with a small list of trusted servers, or to block some specific servers. The maximum allowed delay for retry to connect after a failed connection attempt. Specified in seconds. The default value is 300 seconds (5 minutes).
{max_fsm_queue, Size}
-This option specifies the maximum number of elements in the queue of the FSM. +This option specifies the maximum number of elements in the queue of the FSM +(Finite State Machine). +Roughly speaking, each message in such queues represents one XML +stanza queued to be sent into its relevant outgoing stream. If queue size +reaches the limit (because, for example, the receiver of stanzas is too slow), +the FSM and the corresponding connection (if any) will be terminated +and error message will be logged. +The reasonable value for this option depends on your hardware configuration. +However, there is no much sense to set the size above 1000 elements. This option can be specified for ejabberd_service and ejabberd_c2s listeners, or also globally for ejabberd_s2s_out. @@ -2750,6 +2766,12 @@ to listen for. Default is an IP address of the service’s DNS name, or, if fails, {127,0,0,1}.
{port, Number}
This option defines port to listen for incoming connections. Default is 7777. +
{hostname, HostName}
Defines a hostname advertised +by the service when establishing a session with clients. This is useful when +you run the service behind a NAT. The default is the value of ip option. +Examples: "proxy.mydomain.org", "200.150.100.50". Note that +not all clients understand domain names in stream negotiation, +so you should think twice before setting domain name in this option.
{auth_type, anonymous|plain}
SOCKS5 authentication type. Possible values are anonymous and plain. Default is anonymous. @@ -2881,6 +2903,10 @@ Register a new account on the server. rules to restrict registration. If a rule returns ‘deny’ on the requested user name, registration for that user name is denied. (there are no restrictions by default). +
{access_from, AccessName}
By default, ejabberd +doesn’t allow to register new accounts from s2s or existing c2s sessions. You can +change it by defining access rule in this option. Use with care: allowing registration +from s2s leads to uncontrolled massive accounts creation by rogue users.
{welcome_message, Message}
Set a welcome message that is sent to each newly registered account. The first string is the subject, and the second string is the message body. -- 2.40.0