Working With Log Files > Rolling event log files
|
|
The format of the file (for example, squid.log).
|
|
Two timestamps separated by a hyphen (-). The first time stamp is a lower bound for the time stamp of the first record in the log file. The lower bound is the time when the new buffer for log records is created. Under low load, the first time stamp in the filename can be different from the timestamp of the first entry. Under normal load, the first time stamp in the filename and the time stamp of the first entry are similar.
|
|
The suffix .old, which makes it easy for automated scripts to find rolled log files.
|
1.
|
2.
|
3.
|
In the Offset Hour field, enter a specific time each day you want log file rolling to take place. Content Gateway forces the log file to be rolled at the offset hour each day.
|
4.
|
In the Interval field, enter the amount of time Content Gateway enters data in the log files before rotation takes place.
|
5.
|
Ensure the Auto-Delete Rolled Files option is enabled (the default). This enables auto deletion of rolled log files when available space in the log directory is low.
|
6.
|
Click Apply.
|
You can fine tune log file rolling settings for a custom log file in the LogObject specification in the logs_xml.config file. The custom log file uses the rolling settings in its LogObject, which override the default settings you specify in the Content Gateway manager or the records.config file described above.
|
Working With Log Files > Rolling event log files
|