Fix documentation about file descriptor limits.

This commit is contained in:
Jan Vidar Krey 2010-02-05 22:40:35 +01:00
parent 4715815ba2
commit 78ae9fb3ce
3 changed files with 16 additions and 22 deletions

13
README
View File

@ -3,15 +3,6 @@ Welcome and thanks for downloading uHub, a high performance ADC p2p hub.
For the official documentation, bugs and other information, please visit: For the official documentation, bugs and other information, please visit:
http://www.uhub.org/ http://www.uhub.org/
Compatible ADC clients For a list of compatible ADC clients, see:
http://www.adcportal.com/wiki/index.php/ADC_Software_List#Client_Software
Windows:
- StrongDC
- ApexDC 1.1.x and newest
- Jucy
- RSX++
Unix\Linux:
- Linuxdcpp 1.1.x+ and newest
- FreeDC++
- EiskaltDC++

View File

@ -44,12 +44,14 @@ Example:
% uhub -f -l mylog.txt -u nobody -g nogroup % uhub -f -l mylog.txt -u nobody -g nogroup
If you are planning to more than 1000 users on hub, you must increase the number of max descriptor limits. If you are planning to more than 1024 users on hub, you must increase the max number of file descriptors allowed.
The descriptor limits must be great than the value of max_users uhub.conf. This limit needs to be higher than the configured max_users in uhub.conf.
In linux you must add the following line in /etc/security/limits.conf (for max_users = 4000 ): In linux can add the following lines to /etc/security/limits.conf (allows for ~4000 users)
* soft nofile 4096 * soft nofile 4096
* hard nofile 4096 * hard nofile 4096
Or, you can use (as root):
% ulimit -n 4096
Your mileage may vary -- Good luck! Your mileage may vary -- Good luck!

View File

@ -4,7 +4,7 @@
# #
# This file is read only to the uhub deamon, and if you # This file is read only to the uhub deamon, and if you
# make changes to it while uhub is running you can send a # make changes to it while uhub is running you can send a
# HUP signal to it ( $ killall -HUP uhub ), to reparse configuration (only on UNIX). # HUP signal to it ( $ killall -HUP uhub ), to reparse configuration (only on UNIX).
# All configuration directives: http://www.uhub.org/config.php # All configuration directives: http://www.uhub.org/config.php
# Bind to this port and address # Bind to this port and address
@ -43,7 +43,7 @@ file_acl=/etc/uhub/users.conf
file_motd=/etc/uhub/motd.txt file_motd=/etc/uhub/motd.txt
# This file can contain a rules of the hub. # This file can contain a rules of the hub.
# Normally this message is sent to clients when write in chat !rules # Normally this message is sent to clients when write in chat !rules
file_rules=/etc/uhub/rules.txt file_rules=/etc/uhub/rules.txt
@ -56,19 +56,20 @@ limit_min_hubs_user = 0
limit_min_hubs_reg = 0 limit_min_hubs_reg = 0
limit_min_hubs_op = 0 limit_min_hubs_op = 0
limit_min_share = 0 limit_min_share = 0
# Example: # Example:
# To require users to share at least 1 GB in order to enter the hub: # To require users to share at least 1 GB in order to enter the hub:
# limit_min_share = 1024 # limit_min_share = 1024
limit_max_share = 0 limit_max_share = 0
limit_min_slots = 0 limit_min_slots = 0
limit_max_slots = 0 limit_max_slots = 0
# chat control # chat control
# if chat_is_privileged=yes only REG\OP\OWNER may write in main chat # if chat_is_privileged=yes only registered users may write in main chat
chat_is_privileged = no chat_is_privileged = no
# if chat_only = yes hub block SEARCH\DOWNLOAD # if chat_only = yes then search and transfer functionality is disabled for
chat_only = no # non-operator users.
chat_only = no
# Configure status message as sent to clients in different circumstances. # Configure status message as sent to clients in different circumstances.
msg_hub_full = Hub is full msg_hub_full = Hub is full