
Avaya Media Processing Server Series System Reference Manual
Page 190 # P0602477 Ver: 3.1.11
Consolidation of Log Files
By default log files are created whenever ZAP is used, and are never overwritten.
While administration of these files is left to the discretion of the user, this can
eventually lead to disk saturation if files are not off-loaded or deleted. To reduce this
need for manual intervention, use the -C option to consolidate the files.
Use of the -C option must be consistent: all instances of ZAP must either use it or
leave it out. When instituted, ZAP initially creates the individual log files as it would
without the option: however, when the ZAP process completes, each individual file is
merged into the corresponding consolidated log file. A maximum of seven files are
created if using ZAP on a proxy basis; four files are created if using ZAP without
proxies (these numbers do not include backup files). The zap.debug.log file is
created as usual. The other files are consolidated into the following:
For instances of ZAP started on the local node:
• zap.status.log
• zap.results.log
• zap.distribute.log
For instances of ZAP that use the local node as a proxy:
• zap.status.proxy.log
• zap.results.proxy.log
• zap.distribute.proxy.log
Each consolidated file can reach a maximum size of 1 MB. When this limit is reached,
the file is appended with a .bak extension and a new file created. If this new file
then reaches the maximum size, it too is renamed and the previous backup file is
replaced by it.
If ZAP is used without the -E option, then run later the same day with the option for
the same command, the log file generated earlier in the day is merged along with the
latest one into the consolidated log file.
Kommentare zu diesen Handbüchern