KAVA3650-I
Information about startup of the log file trap (ID = process-ID/thread-ID): conf-file = action-definition-file-name, last updated = YYYY/MM/DD hh:mm:ss, options = option-information, watch-file = name-of-the-monitored-file1 name-of-the-monitored-file2...
This message outputs startup information of the log file trap.
Startup information |
Description |
---|---|
process-ID/thread-ID |
If the monitored name is specified during startup, this item is output in the following format: id = process-ID[monitored-name]/thread-ID[monitored-name] |
action-definition-file-name |
The absolute path to the target action definition file is output. |
YYYY/MM/DD hh:mm:ss |
The time when the target action definition file was last saved is output. |
option-information |
This item is output in the following format: options = file-monitoring-interval-in-seconds|maximum-length-of-the-data-to-be-changed-to-an-event-in-bytes|whether-to-read-data-from-the-beginning-of-the-log-file-by-yes-or-no|displayed-command-name (in UNIX only)|name-of-the-program-that-outputs-log-data|whether-to-wait-until-the-log-file-is-opened-by-yes-or-no|registration-destination-event-server-name|whether-to-monitor-UNICODE-files-by-yes(UTF-8)-or-yes(UTF-16)-or-no (in Windows only)|UNICODE-file-byte-order-specification (in Windows only)
|
name-of-the-monitored-file |
The absolute path to the monitored target file specified during startup is output. If you specified multiple monitored target files, they are output, separated by spaces. If all of the monitored target file names cannot be output because of the message length limitations, the file names are output up to the maximum allowable length, and the forward slash (/) is output at the end of the message. |
#: For UNIX, this portion is UX_LOGTRAP.