Log rotation and log cleanup

In the default configuration, most CM Server log files are piped to the rotatelogs program, which periodically creates a new log file. The following line (which has been split into two lines to fit here) uses rotatelogs to create a new copy of the accesserror.log file every 86,400 seconds (24 hours).
CustomLog "|\"/opt/IBM/RationalSDLC/common/IHS/bin/rotatelogs.exe\" \"
/opt/IBM/RationalSDLC/common/IHS/logs/access.log\" 86400" common

The log rotation period begins when CM Server is started.

For every application, except Rational® ClearCase®, IBM® HTTP Server log files accumulate, so you must clean them periodically. Rational ClearCase deletes the old logs during its weekly log scrubbing job, removing all CM Server log files that are older than 30 days. You can modify this job to change the frequency with which the job runs, the age of the log files it removes, or any other aspect of its operation.

Note: If you change any of the default CM Server log locations, you must also modify the cleanuplogs script so that it looks for these logs in their new location.
On CM Server hosts that do not have Rational ClearCase installed, you must periodically run one of the following programs to remove old log files:

Use a scheduled-execution program supplied by the operating system (cron, for example, on the UNIX system, or at on Windows) to run these scripts, or run them manually.


Comentarios