Changeset 619

Timestamp:

07/04/08 02:03:42 (7 weeks ago)

Author:

markdoliner

Message:

Hopefully make the documentation for max_fds more clear for people who
aren't programmers and aren't familiar with how jabberd works.

Location:

trunk/etc

Files:

• c2s.xml.dist.in (modified) (1 diff)
• router.xml.dist.in (modified) (1 diff)
• s2s.xml.dist.in (modified) (1 diff)

trunk/etc/c2s.xml.dist.in

@@ -174 +174 @@
   <!-- Input/output settings -->
   <io>
-    <!-- Maximum number of file descriptors. Note that the number of
-         possible connections will be slightly less than this, because
-         c2s itself can use up five on its own, and auth/reg modules may
-         need a few also. If the supply of file descriptors is
-         exhausted, new incoming connections will be denied.
+    <!-- Maximum number of file descriptors. This value sets an upper
+         limit on the number of users who may be logged in to this
+         server at a given time. Each user consumers one file
+         descriptor.
+
+         Note that the number of possible connections will be slightly
+         less than this, because c2s itself can use up five on its own,
+         and auth/reg modules may need a few also. If the supply of
+         file descriptors is exhausted, new incoming connections will
+         be denied.
+
+         Also note that this value only affects how many file descriptors
+         jabberd is able to handle internally. You may also need to
+         tell your operating system to allow jabberd to use more file
+         descriptors. On Linux this can be done using ulimit -n or by
+         changing the value of /proc/sys/fd/file-max.
+
          (default: 1024) -->
     <max_fds>1024</max_fds>

trunk/etc/router.xml.dist.in

@@ -82 +82 @@
          the router itself can use up four on its own. If the supply of
          file descriptors is exhausted, new incoming connections will be
-         denied (default: 1024) -->
+         denied.
+
+         These file descriptors are really only used when a component
+         connects to the router. So unless you have a lot of components
+         for some reason then you probably don't need to change this
+         value.
+
+         (default: 1024) -->
     <max_fds>1024</max_fds>
 

trunk/etc/s2s.xml.dist.in

@@ -122 +122 @@
          s2s itself can use some on its own. If the supply of file
          descriptors is exhausted, new incoming connections will be
-         denied (default: 1024) -->
+         denied.
+
+         These connections are mainly consumed when we make a
+         connection to an external jabber server, or an external jabber
+         server connects to us. If you don't have a lot of users then
+         there's probably no need for s2s to establish connections to
+         external jabber servers and the default value here is probably
+         fine. On the other hand, if you have lots of users with lots
+         of remote buddies in their buddylist then s2s will need to have
+         lots of open connections with other jabber servers and you may
+         need to increase this value.
+
+         Note that this value only affects how many file descriptors
+         jabberd is able to handle internally. You may also need to
+         tell your operating system to allow jabberd to use more file
+         descriptors. On Linux this can be done using ulimit -n or by
+         changing the value of /proc/sys/fd/file-max.
+
+         (default: 1024) -->
     <max_fds>1024</max_fds>