Lists all the general settings for your server.
Example:
/as general list
This is used to check how your server is currently set up. You can use it to confirm that you made changes you intended to make. It will show you the server's name, description, contact info, serial number, ports, oper host, the number of users allowed, whether dns resolution is on, and whether it is a hub or a leaf.
Defines the use of the MJOIN command. When a user mjoins a channel a bot is placed in a master channel and the user is joined to sub channels. The bot will set the modes, limit, max and min as set using the commands listed below. When the last user leaves the sub channel the entire channel will disappear. It acts like join but using the Auditorium Rows logic.
BOT - Define which bot will manage the mjoined channels.
DEFAULT - Uses the mjoin command for all join commands.
LIMIT - Sets the Rows User Limit.
MAX - Sets the Rows User Maximum.
MIN - Sets the Rows User Minimum.
MODES - Set the default channel modes.
OFF - Turns off the mjoin capability.
ON - Enable mjoin capability.
Example:
/as help general mjoin <command> <setting>
MJOIN acts like join with the exception that users are automatically joining channels that use the auditorium system. This is handy when you do not want channel sizes to get to large on your server, or you have specific needs to keep your channels at certain user numbers. This uses the auditorium rows feature which allows you to send messages in a master channel that go to all sub-channels.
The name server allows your server to recognize the IP addresses of host names. You should try to always have a functioning name server added. Removing name servers from a running server is not recommended unless the name server is dead. You can have multiple name servers added and can add one of WebMaster's core name servers by adding default.
ADD - Add a nameserver
DEL - Delete a namserver
LIST - Display your namserver setup
Examples:
/as help general nameserver <topic>
Once initially configured, you should not need to change this setup. However, if you know that one of your name servers is no longer responding then you should delete it.
Personal Logging (PLog) is a feature that allows users to create a log of their user and channel messages, once enabled the logging will remain enabled for the entire session regardles of how long that is. As the log file grows in length and hits the maximum size a new file will be created and the older files emailed to the address in the email user property.
All log files are encrypted and signed with the servers certificate and it takes a special tool to view them. The servers signature is a method you can use to validate the chat session to insure that the text has not been modified or altered. This method should meet all court requirements (check your local jurisdiction for specific rules). You can check http://www.webmaster.com/plog/ for availability of that tool. Also crws can view Personal Log files.
When you check the status of your session you can go to http://yourserver.com/plog.html and view the file in progress. PLog files are not in real time and may lag your conversation by several minutes.
DISABLE - Turns of Personal Logging.
ENABLE - Enables Personal Logging.
SET - Sets specific features.
Example:
/as general plog enable
Sets specific information such as your server's name, description and contact information.
ANNOUNCE - Announce that you can take overflow users.
AUP - Set an Acceptible Use Policy URL.
CONTACT - Set the administrator's contact information.
DESCRIPTION - Set the description for the server.
DNS - Turn on or off DNS resolution.
DOMAIN - Report to the domain controller.
DOMAINKEY - Sets the Domain Key
ECHO - Server side text echo.
HEAPMIN - Heap Minimization
HOST - Set the hostname for the server.
HUB - Set the server as a hub.
KEY - Enter a ConferenceRoom License Key.
LEAF - Set the server as a leaf.
LIMIT - Limit the number of users that can log on.
LISTENQUEUEDEPTH - This sets the depth of the listen queue for chat sockets.
LOGROTATE - Rotate logs every day.
NAME - Set the server name.
NETWORK - The single word name for your chat server.
OPERHOST - Set the domain (spoofed) for all Operators.
POOLBLOCKSIZE - Sets the size (in bytes) of each block in the server's emergency memory pool.
POOLCOUNT - Sets the number of blocks in the server's emergency memory pool.
PORTS - Set the ports that clients can use to connect.
REDIRECT ON SHUTDOWN - Send users to another server when unavailable.
SECURENETWORK - Sets an Encryption only network.
SECUREONLY - Sets a server to only accept encrypted sessions both client and server.
SHORTNAME - Sets the server or network shortname.
SMARTLIST - Unifies Master/Slave channel reporting in /list to a single channel and user count.
TIMESTAMP - Adds a timestamp to all messages.
Example:
/as help general set <command>
It is a good idea to go through all of the general settings before opening your server for use.
These commands setup and control Secure Socket Layer connections. They allow for encrypted connections.
CERTFILE - Set the SSL certificate.
CHAINFILE - Sets a file containing the certificate chain (in PEM format).
DISABLE - Disable SSL.
ENABLE - Enable SSL.
KEYFILE - Set the SSL key.
PORT - Set the port for secure connections.
UPDATE - Recieve T7 country updates.
V2 - Enables SSL V2 Support.
Example:
/as general ssl enable
Set the time servers that will synchronize your chat server's time. You can specify WebMaster's time servers by adding "default".
ADD - Add a time server
DEL - Remove a time server
LIST - List your time servers
Examples:
/as help general timeserver <topic>
In a clustered environment having all of your servers in synch will create a more stable environment for the users. There is logic inside the chat server to make sure that topics and modes are set correctly and this is based on the time and rank of the user that set the mode or topic. If one of your servers is out of synch time wise you could get topic or mode bounces, be unable to set or change topics or get channel modes.