|
|
| Administration Console Settings |
| Admin Server is a special virtual host dedicated to the web administration console.
It is very important to make sure Admin Server is securely protected either by only allowing
access from administrator's machines or by using encrypted SSL connection.
|
| |
| Table of Contents |
|
| |
| Enable Core Dump |  |
|
| Description: Specifies whether to enable core dump when server is started by "root" user.
For most modern Unix systems, processes that changes user id or group id is not allowed to
dump a core file for security reasons. However, it is much easier to identify root
cause of a problem with a core dump. This option only works on Linux with kernel >2.4.
Solaris users should use coreadm command to control this feature.
|
| Syntax: Select from radio box |
| Tips: [Security] Only enable it when you see no core file is created in
server log file and disable it immediately after producing the core file.
Please submit a bug report when core dump is created. |
|
| Session Timeout (secs) | |
|
| Description: Customize the session timeout of WebAdmin Console.
Default is 60 secs if no value is set.
|
| Syntax: Integer number |
| Tips: [Security] Set a proper value for production use, usually should be
less than 300 seconds. |
|
| Use Server Log | |
|
| Description: Specifies whether to put log messages from this virtual host into server
log file instead of creating its own log file.
|
| Syntax: Select from radio box |
|
| File Name | |
|
| Description: Specifies the server log file.
|
| Syntax: File name which can be an absolute path or relative to $SERVER_ROOT. |
| Tips: [Performance] Place log file on a separate disk. |
|
| Log Level | |
|
| Description: Specifies the level of logging. Available levels are ERROR,
WARNING, NOTICE, INFO and DEBUG from high to low.
Only messages with higher level than current setting will be logged.
If you want to set it to DEBUG, you must set server log level to be DEBUG as well.
The level of debugging is solely controlled by Debug Level.
|
| Syntax: Select from drop down list |
| Tips: [Performance] Unless Debug Level is set to a level
other than NONE, DEBUG log level does not have any
performance impact and is recommended. |
| See Also: Debug Level |
|
| Rolling Size | |
|
| Description: Specifies when the current log file needs to be rolled over, also known as log rotation.
When the file size is over the rollover limit, the active log file will be renamed
to log_name.mm_dd_yyyy(.sequence) in the same directory and a new active log file will be created.
The actual size of the rotated log file could be a little bigger. Set
to 0 to disable log rotation.
|
| Syntax: Integer number |
| Tips: Append "K", "M", "G" to the number for kilo-, mega- and giga- bytes |
|
| Log Control | |
|
| Description: Specifies where to write access log. There are three options:
1. write to server's access log; 2. create its own access log; 3. disable access logging.
|
| Syntax: Select from drop down list |
|
| File Name | |
|
| Description: Specifies the file name of the access log file.
|
| Syntax: File name which can be an absolute path or relative to $SERVER_ROOT. |
| Tips: [Performance] Put access log file on a separate disk. |
|
| Piped Logger | |
|
Description: Specifies the external application that will receive the access log
data sent by LiteSpeed through a pipe on its STDIN stream (file
handle 0). When specified, access log will be sent only to the logger application but not the
access log file specified in previous entry.
Logger process is spawned in the same way as other external (CGI/FastCGI/LSAPI) processes,
which means it will execute as the uid according to the virtual host's
configuration of ExtApp Set UID Mode,
and will never run on behalf of a privileged user.
The logger application must
be defined in External Application section first. Server level access
logging can only use external logger application
defined at server level, while virtual host level access log can only use
logger application defined at virtual host level.
The LiteSpeed server
performs simple load balancing among multiple logger applications if
more than one instance of logger application is configured.
LiteSpeed server always attempts
to keep the number of logger application as low as possible. Only when one
logger application failed to process access log entries in time will the
server attempt to spawn another instance of logger application.
If a logger crashes, the web server will start another instance but the log data in the stream buffer will be lost.
It is possible to lose log data if external loggers cannot keep up with the speed and volume of the log stream.
|
| Syntax: Select from drop down list |
|
| Log Format | |
|
| Description: [Enterprise Edition Only] Specifies the log format for access
log. When log format is set, it will override Log Level
setting. The syntax of log format is compatible with
Apache
2.0's custom log format.
|
| Syntax: string |
|
| Log Headers | |
|
| Description: Specifies whether to log HTTP request headers: Referer,
UserAgent, and Host.
|
| Syntax: Select from checkbox |
| Tips: [Performance] Turn it off if you do not need these headers in the access log. |
|
| Keep Days | |
|
| Description: Specifies how many days the access log file will be kept on disk.
Only rotated log file older than specified days will be deleted and the active current
log file will not be touched regardless how many days' data it contains.
If you do not want to auto-delete stale and very old log files,
set this value to 0.
|
| Syntax: Integer number |
|
| Bytes Log | |
|
| Description: Specifies the path to the bandwidth bytes log file. When
specified, a CPanel compatible bandwidth log will be created. Will log
the total bytes transfered for a request including both
request and reply body.
|
| Syntax: File name which can be an absolute path or relative to $SERVER_ROOT. |
| Tips: [Performance] Put the log file on a separate disk. |
|
| Compress Archive | |
|
| Description: Specifies whether to compress rotated log files in order to save disk space.
|
| Syntax: Select from radio box |
| Tips: Log files are highly compressible and this is recommended to reduce disk usage for old logs. |
|
| Access Control | |
|
| Description: Specifies what sub-network and/or IP address can access this virtual host
in addition to server level access control. Virtual host setting does NOT override
the server setting. Whether to block/allow an IP is determined by the combination
of allowed list and denied list. If you want to block certain IP or sub-network,
put * or ALL in the allowed list and list the blocked IP or
sub-network in the denied list. If you want to only allow certain IP or sub-network,
put * or ALL in the denied list and list the allowed IP or
sub-network in the allowed list. The setting of the smallest scope that fits for
an IP will be used to determine whether to block or allow access. |
|
| Allowed List | |
|
| Description: Specifies the list of IP or sub-net allowed.
|
| Syntax: comma-separated list of IP address or sub-network. * or ALL,
sub-network can be like 192.168.1.0/255.255.255.0, 192.168.1 or 192.168.1.*. |
|
| Denied List | |
|
| Description: Specifies the list of IPs or sub-networks disallowed.
|
Syntax: Comma separated list of IP address or sub-network, * or ALL,
sub-network can be like
192.168.1.0/255.255.255.0, 192.168.1.0/24, 192.168.1 or
192.168.1.*.
IPv6 address should be like ::1 or [::1], IPv6 subnet
should be like 3ffe:302:11:2:20f:1fff:fe29:717c/64 or
[3ffe:302:11:2:20f:1fff:fe29:717c]/64. |
|
| Admin User | |
|
| Description: Change user name and password for WebAdmin Console. There is a limit of
one admin user. Click Edit to change user name or
password. Old password has to be entered and verified in order to save
the changes.
|
| Tips: If you forget the admin password, you cannot change it from the
Web Administration Console. Please use the following command from shell:
[your install dir]/admin/misc/admpass.sh |
|
| |
|
|
| |
Copyright © 2003-2007. Lite Speed Technologies Inc.
All rights reserved. |