GENERAL SET CONTACT

    Usage: GENERAL SET CONTACT <value>

    Allows you to have a point of contact for your server. This lets people using the server know how to contact the administrator. This information is available when the /admin command is used.

    Example:
    /as general set contact sales@webmaster.com

    The contact field cannot contain any spaces. You should probably put a fairly self-explanatory email address in it. You should expect this email address to get all sorts of questions since many users may see it as a first place to turn if they cannot find out whom else to email. You might want to put contact info into a motd in addition, since it is more noticeable and you can use up more space.


    GENERAL SET DESCRIPTION

    Usage: GENERAL SET DESCRIPTION [<value>]

    This is a short description of your server that will be displayed when a user types the /admin or /info commands or in a /links command.

    Example:
    /as general set description ConferenceRoom 1.8

    You can use this to give people some information about the server they are using. If the server is run by a company you may want to put a brief statement about the company, perhaps including its URL.


    GENERAL SET DNS

    Usage: GENERAL SET DNS [on|off]

    If you turn this off then client addresses will appear as IP addresses rather than as host domains.

    Examples:
    /as general set dns on
    /as general set dns off

    You will usually want this on; otherwise everyone will appear to come from numeric addresses. There's nothing wrong with everyone coming from numeric addresses, but it doesn't look quite as nice. Whichever you choose, you should do consistently, so that people will usually match their access lists.


    GENERAL SET DOMAIN

    Usage: GENERAL SET DOMAIN [<domain>]

    This command is to set your domain name for the community listing of ConferenceRoom servers. If you decide to join, your IP will be listed at www.ConferenceRoom.net. To enable this feature you need to email your serial number, domain name, and domain password to crdomains@conferenceroom.net. Your server will be accessible using the format domain.conferenceroom.net. Leaving out a domain name will cause the server to erase the current setting. The example below would be listed as webmaster.conferenceroom.net and resolve to irc.webmaster.com.

    Example:
    /as general set domain webmaster


    GENERAL SET DOMAINPASS

    Usage: GENERAL SET DOMAINPASS [<password>]

    This command will set the domain password for the ConferenceRoom community listing. Leaving the password blank will delete the current password. See GENERAL SET DOMAIN for more information.

    Example:
    /as general set domainpass mYp455


    GENERAL SET HEAPMIN

    Usage: GENERAL SET HEAPMIN on|off

    By default, the WIN32 version of ConferenceRoom attempts to return unused memory back to Windows (heap minimization). This behavior can be disabled.

    Example:
    /as general set heapmin off

    There should normally be no reason to turn heap minimization off. This option does not exist on UNIX versions of ConferenceRoom.


    GENERAL SET HOST

    Usage: GENERAL SET HOST <value>

    This option locks your server to a specific hostname. It is only useful if you have a static ip address.

    Example:
    /as general set host server1.webmaster.com

    This option should be left off unless you have an IP address that does not change each time you connect to your provider and you need to lock your server to a specific hostname. This may sometimes be necessary when using the Java interface with your server, but only in rare cases.


    GENERAL SET HUB

    Usage: GENERAL SET HUB

    This command will set your server as a hub server. This way you will be able to allow servers to connect to your server and allow downstream connections.

    Example:
    /as general set hub

    A network is composed of hubs and leafs. The hubs should be the stablest servers with the best capacities. You should also generally limit the user count on the hub servers since they will be handling more information, holding the network together. The leaf servers work as client servers, supporting the majority of the user base. Hubs are the backbone of the network.


    GENERAL SET KEY

    Usage: GENERAL SET KEY <key>

    ConferenceRoom comes with a trial key that enables the server for 30 days. When purchasing a copy of ConferenceRoom a key is sent to you. Place the key in that field, your server will then be registered with what ever level purchased.

    Example:
    /as general set key K342-L2O1-L2FE-98B2

    This is a necessary part of the registration process; or else your server will not realize that you have bought a license. After the key is set it will display a registration code rather than the key itself in any place where the information is given. If you upgrade your key, you use this command to make the upgrade take effect. For more information on upgrading safely, please see the FAQ.


    GENERAL SET LEAF

    Usage: GENERAL SET LEAF

    This command will set your server as a leaf server. This will allow you to connect to a hub server.

    Example:
    /as general set leaf

    A leaf can only connect to one server. It will not have to handle as much network traffic as a hub server, so it should be able to handle more clients. If it splits off then only the users on that server are separated from the network until it reconnects. If it dies then the users can reconnect onto another server, but the network is not split. A network will usually have many more leafs than hubs, usually at least twice as many unless it has a small number of servers.


    GENERAL SET LIMIT

    Usage: GENERAL SET LIMIT <number>

    It is possible to support up to 10, 000 simultaneous users with the correct machine configuration on ConferenceRoom. There is a limitation on the number of simultaneous connections depending upon the end user license. It is automatically set to 10 for the trial version.

    Example:
    /as general set limit 1000

    You can choose to set your user limit lower than what your license permits. You might want to do this if you found that your server was having difficulty handling large numbers of clients or if it were a hub and you did not want to overload it. Your server's abilities will depend on the machine it is running on. Experience will probably help you determine what number of clients is right for your server.


    GENERAL SET LISTENQUEUEDEPTH

    Usage: GENERAL SET LISTENQUEUEDEPTH <value>

    This sets the depth of the listen queue for chat sockets.

    Example:
    /as general set listenqueuedepth 32

    The default varies by operating system and generally should not be changed. You may wish to decrease this value if you want to listen on a lot of ports and want to minimize network resource usage. You may wish to increase this value if to increase your server's ability to resist TCP SYN floods.


    GENERAL SET LOGROTATE

    Usage: GENERAL SET LOGROTATE [on|off]

    Log rotation causes a new log to be started every day. The log file will be named after the day of the year for which it holds entries. This affects both chat and web server logs but does not (yet) affect services logs.

    Example:
    /as general set logrotate on

    This can be useful to make information easier to find. You can create an archive of logs and look up any information you need based on when it happened.


    GENERAL SET NAME

    Usage: GENERAL SET NAME <name>

    This field is the name you assign to your server. It does not have to be the hostname of your computer (though that is recommended). This name will be seen by users when they log into your server, and by other servers networking with your server. It is suggested that you consider that when you choose a name. While you may choose almost any name, it must not have any spaces in it.

    Example:
    /as general set name irc.webmaster.com

    It is generally a good idea to have a uniform naming scheme for all the servers on your network, to make it easier for people to remember them. While most people do not need to know the server names, it is important for the network operators who may need to route servers. It also looks nicer and more professional if all of the servers follow the same pattern.


    GENERAL SET NEWHELP

    Usage: GENERAL SET NEWHELP <on|off>

    The 1.8.6 version of ConferenceRoom contains a new help system that brings both online help and the manual current. Because of this we no longer use the help files that were located in the /db folders. Some customers may have customized those files and want a method to return the server to its previous setup using the old help system and their modified files.

    Example:
    /as general set newhelp off

    Use the prior help system.


    GENERAL SET OPERHOST

    Usage: GENERAL SET OPERHOST <domain>

    Changes the host name for any user that is set +o (operator).

    Example:
    /as general set operhost conferenceroom.com

    In some cases where it is approproate to protect the identity and location of your server operators you can set the host name that it will appear they come from.


    GENERAL SET POOLBLOCKSIZE

    Usage: GENERAL SET POOLBLOCKSIZE <value>

    Sets the size (in bytes) of each block in the server's emergency memory pool. The server allocates the emergency pool on startup and frees pieces of it when memory is tight.

    Example:
    /as general set poolblocksize 16384

    The default is 8Kb on all operating systems except Linux where the default is 128Kb. You may wish to lower this value if your server is tight on memory. You may wish to raise this value to allow your server to better handle memory exhaustion situations.

    Note: Making the memory pool too small can destabilize the server.


    GENERAL SET POOLBLOCKCOUNT

    Usage: GENERAL SET POOLCOUNT <value>

    Sets the number of blocks in the server's emergency memory pool. The server allocates the emergency pool on startup and frees pieces of it when memory is tight.

    Example:
    /as general set poolcount 32

    The default is 24 blocks on all operating systems except Linux where the default is 10. Making the memory pool too small can destabilize the server. Generally, it is better to increase the size of each block than increase the number of blocks in the pool.


    GENERAL SET PORTS

    Usage: GENERAL SET PORTS <port numbers>

    This command designates the port(s) to be allocated for users to connect to the server. The default port, as is usually the case for chat networks, is set for 6667. To specify multiple ports, separate them by commas (i.e. 6667,7000). To specify a range of ports, use a dash to indicate the beginning and ending ports (i.e. 7000-7020).

    Note that you can mix these specifications (i.e. 6667, 7000- 7020 accepts connections on port 6667 and port 7000 through 7020). The first port used in this field will designate which port the web-based clients connect on. This can be important when you are trying to let sites connect that firewall the standard chat ports. ConferenceRoom comes defined with 7000, 6667. This means that java client will connect on port 7000. IP Binding: It is possible to bind IPs together, here is an example:

    /as general set ports 4300,7300:127.0.0.1,6667:208.107.4.8,7325:219.49.56.10

    Examples:
    /as general set ports 7000,6660-6669
    /as general set ports 4535,7777:127.0.0.1,6667-6669

    If possible you should allow clients to connect on 7000 and 6667 since many users expect to be able to use those ports. 8000 is a good port for the web server, and the default.


    GENERAL SET SECURENETWORK

    Usage: GENERAL SET SECURENETWORK [on|off]

    This turns on or off encryption for all server to server communications. This allows the room mode z to be used and for secure messaging across servers.

    Example:
    /as general set securenetwork on


    GENERAL SET SECUREONLY

    Usage: GENERAL SET SECUREONLY [on|off]

    When set on, only secure connections will be allowed.

    Example:
    /as general set secureonly on


    GENERAL SET SMARTLIST

    Usage: GENERAL SET SMARTLIST [on|off]

    If smartlist is on, the master channel will show and the user count is the sum for all the slaves. If smartlist is off then the master channel and each slave channel will show separately in the list.

    Example:
    /as general set smartlist on