Show
Ignore:
Timestamp:
04/07/08 02:03:42 (5 months 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.

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • trunk/etc/c2s.xml.dist.in

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