iTP Secure WebServer System Administrators Guide (Version 7.5+)

been changed in the configuration file, the iTP Secure WebServer ignores the change and
opens new files using the old names.
When you use -rollover with -start, the log files that were in use when the iTP Secure
WebServer was stopped are saved on startup, and the httpd process begins logging to new
files. If the log file names have been changed in the configuration file, the server opens new
files using the new names.
When you use -rollover with -restart, the current log files are saved when the iTP
Secure WebServer is stopped, and the httpd process begins logging to new files when it is
started again. If the log file names have been changed in the configuration file, the server
opens new files using the new names.
When you use -rollover with -restarth, the current log files are saved, and the httpd
process begins logging to new files. If the log file names have been changed in the
configuration file, the server opens new files using the new names.
When you use -rollover with -stop, the current log files are saved before the httpd process
is stopped. When the iTP Secure WebServer is started again, it begins logging to new files.
When you use -rollover with -add, the log files that were in use when the iTP Secure
WebServer is started, are saved on addition, and the httpd process begins logging to new
files. If the log file names have been changed in the configuration file, the server opens new
files using the new names.
When you use -rollover with -delete, the current log files are saved before the deletion.
When the iTP Secure WebServer is started/added again, it begins logging to new files.
NOTE: If no disk space is available to save the current log files, a message (#580) appears on
the command line. Logging stops, and the iTP Secure WebServer reports to the Event Management
Service (EMS) that it cannot write to the log files. To recover from this condition, either provide
more disk space for the logs or, if the log files are very large, archive or delete them and restart
the httpd process.
PATHMON Environment's Autorestart for the iTP Secure WebServer and
Related Processes
Because the iTP Secure WebServer and related processes run in a PATHMON environment, a process
that fails is restarted automatically, ensuring persistence of its service. (PATHMON does not
automatically restart a process that the operator has explicitly stopped.)
Collecting httpd Statistics Using statscom
iTP Secure WebServer performance statistics can be collected from the iTP Secure Administration
WebServer. Because the webserver administrator only can access this server, it is not possible for
normal users to collect webserver statistics. Also, this process is manual and cannot be automated
for scheduled statistics collection.
To overcome these problems, iTP Secure WebServer provides a command-line utility that uses the
statscom command to collect webserver statistics. It eliminates the need of administration server
access for performance data collection. Therefore, any user can collect webserver statistics. Also,
the command-line utility makes automated processing possible through the use of shell scripts for
batch processing.
statscom Command
The statscom command performs the following tasks:
1. Starts the webserver instrumentation
2. Stops the webserver instrumentation
88 Managing the iTP Secure WebServer Using Scripts