Руководство Пользователя для Cisco Cisco Content Security Management Appliance M160

 shows the statistics recorded in system logs.

In this example, the system log shows some commit entries, including the name of the user issuing the 
commit and the comment entered.

Wed Sep  8 18:02:45 2004 Info: Version: 6.0.0-206 SN: XXXXXXXXXXXX-XXX

Wed Sep  8 18:02:45 2004 Info: Time offset from UTC: 0 seconds

Wed Sep  8 18:02:45 2004 Info: System is coming up

Wed Sep  8 18:02:49 2004 Info: bootstrapping DNS cache

Wed Sep  8 18:02:49 2004 Info: DNS cache bootstrapped

Wed Sep  8 18:13:30 2004 Info: PID 608: User admin commit changes: SSW:Password

Wed Sep  8 18:17:23 2004 Info: PID 608: User admin commit changes: Completed Web::SSW

Thu Sep  9 08:49:27 2004 Info: Time offset from UTC: -25200 seconds

Thu Sep  9 08:49:27 2004 Info: PID 1237: User admin commit changes: Added a second CLI log 

for examples

Thu Sep  9 08:51:53 2004 Info: PID 1237: User admin commit changes: Removed example CLI 

log.

Tracking logs record information about the email operations of AsyncOS. The log messages are a subset 
of the messages recorded in the mail logs.

The tracking logs are used by the message tracking component to build the message tracking database. 
Because the log files are consumed in the process of building the database, the tracking logs are transient. 
The information in tracking logs is not designed to be read or analyzed by humans.

Tracking logs are recorded and transferred in a binary format for resource efficiency. The information is 
laid out in a logical manner and is human-readable after conversion using a utility provided by Cisco. 
The conversion tools are located at the following URL:
 

http://tinyurl.com/3c5l8r

.

Time that the bytes were transmitted.

The logged event.