System HTTP Mail Servers Security Services Utils  
Overview Configure Logs Manage Performance Reports Network Trace Clock Sync

Configure [config.ini] Help
Changes don't take effect until system restart. You must restart the server before making any other configuration changes or the changes you make below will be overwritten.
Administrator(s)

The System Administrator(s) username is used to access these sysadmin folder and administrator methods. By default, the administrator username is 'admin'. This can be a space-separated list of usernames.
Administrator IP

If left blank, the Sambar Server System Administrator may login from any host. A space-separated list of IP addresses may be provided (the wild-card character '*' may be used, i.e. 140.172.165.* ) to ensure that only hosts which you plan to use for administration have access to your System Administration tools. For maximum security, only allow access to the "localhost" account (127.0.0.1).
Server Port

The TCP/IP protocol has a number of ports which are used to differentiate requests to different processes. The standard HTTP port number is 80. You can choose any port number from 1 to 65000, however, many port numbers on your system are reserved for other applications. Should you choose any port other than port 80, you will have to access you homepage with the port number appended to the URL (i.e. http://www.sambar.com:1080/ ).
Maximum Connections

Configure the maximum simultaneous connections supported by the system. Connections differ from users in that a connection is only maintained by the HTTP server for the duration of the transaction (HTTP request). Therefore, while you might wish to support 200 simultaneous users, the number of simultaneous connections needed to support that number of users would likely be no more than 40.
Idle Threads

Configure the minimum number of idle threads the server should keep around to respond to requests. General rules of thumb should be 5-10 for development machines, and 20-50 for production machines.
Network Read Timeout

Configure the maximum time, in seconds, to wait for a client connection before terminating the connection. This period must be at least as large as the Keep-Alive duration defined for the HTTP protocol. This duration affects HTTP, proxy and FTP clients.
Memory Cache

Configure the size, in bytes, for in-memory caching of disk files. If zero (0) is specified, no file caching is performed. The memory cache is used to enhance the HTTP Server performance only; there is presently no caching mechanism for HTTP Proxy requests. For maximum performance, this should be set to the cumulative size of all static files in your document directories. (Note: The FTP Server and DNS Server also use this memory cache). Important! This should be set to 0 if WebDAV is enabled.
Automatic Log Rotation

If turned on, the server log files (www, server, proxy, mail, dhcp etc.) will be automatically rotated and WWW log and server reports will be automatically run. The log reports are available through the system administration Report interface.
Log Buffer Size

Configure the maximum number of lines permitted in the server log file (server.log). Once this number is reached for a server session, the log is reset to the first line (it operates much like a circular buffer). For an infinite log size, set the log size value to 0.
Act as HTTPS Server

Yes
No

Start the SSL HTTP Server when the Sambar Server is started (in addition to the HTTP server). There are several additional configuration elements associated with installing and running SSL on the Sambar Server. See the SSL documentation for more details.
Act as Mail Server

Yes
No

Start the Mail Server when the Sambar Server is started (in addition to the HTTP server). Additional Mail configuration parameters must be entered via the Mail Configuration forms on the System Administration pages. User mailboxes are created using the User Management forms.
Act as DNS Server

Yes
No

Start the DNS Server/Proxy when the Sambar Server is started. Additional DNS configuration parameters must be entered via the DNS Configuration forms on the System Administration pages. The functionality of this server/proxy is outlined on the DNS system help pages.
Act as FTP Server

Yes
No

Start the FTP Server when the Sambar Server is started (in addition to the HTTP server). WARNING: If your machine is already running an FTP Server, the FTP Server will fail to start if the ports of the two servers conflict.
Act as TFTP Server

Yes
No

Start the TFTP Server when the Sambar Server is started (in addition to the HTTP server). WARNING: If your machine is already running an TFTP Server, the TFTP Server will fail to start if the ports of the two servers conflict. The TFTP supports read-only access to files found in the Sambar Server tftpboot directory.
Act as Telnet Server/Proxy

Yes
No

Start the Telnet Server & Proxy when the Sambar Server is started (in addition to the HTTP server). See the Telnet documentation for usage details.
Act as DHCP Server

Yes
No

Start the DHCP Server when the Sambar Server is started (in addition to the HTTP server). See the DHCP documentation for usage details.
Run Watcher

Yes
No

Start a Watcher Daemon when the server is started to monitor the WWW server and restart it in the event of a failure. This feature can be used when the Sambar Server is run as an NT Service.
Watcher Timeout

Configure the delay in seconds between each wwwping of the server by the watcher daemon. This time should exceed 60 seconds (1200 is the default). After two consecutive connect failures, the Sambar Server will be terminated and restarted by the Watcher Daemon.
NTP Server

Specify an NTP server (network time protocol) to use to synchronize the server's clock with at the specified cron period. See www.ntp.org for a list of public NTP servers. If the NTP server or cron period is left blank, synchronization will not occur. An example cron period would be 0 1 * * * , which equates to every nigth at 1AM.
Cron