iTP Secure WebServer System Administrator's Guide (Version 7.0)

Configuration Directives
iTP Secure WebServer System Administrator’s Guide—523346-012
A-45
Examples
LOG1 <file-name|collector-process|terminal> [status|eventformat]
specifies the logging mode that the PATHMON process and TCP must use to report
errors and changes in object status.
A typical syntax format for the LOG1 attribute is as follows:
LOG1 file-name|collector-process|terminal [logparam1]
[logparam2]
where,
•
file-name specifies the name of a file to receive error reports and changes in
status. If the specified file does not exist, iTP Secure WebServer creates it
automatically. If you specify a pre-existing file, ensure that the specified file is a text
file.
•
collector-process is the name of the collector process for the system.
Currently, iTP Secure WebServer supports only the primary collector process, $0.
•
terminal is any Guardian terminal, in paused state, used to display logging
information about the LOG1 attribute.
•
logparam1, logparam2 can be STATUS or EVENTFORMAT.
Examples
•
The following command logs errors and status change messages in a file named
MYLOG:
LOG1 MYLOG STATUS
where,
MYLOG is the name of the text file where the status information must be stored.
STATUS sends status change messages and error messages to the file MYLOG.
•
The following command logs error messages to the primary collector $0, and
formats the messages as event messages:
LOG1 /G/0 EVENTFORMAT
where,
/G/0 is the primary collector.
EVENTFORMAT specifies that messages must be formatted as event messages. If
you omit EVENTFORMAT, text messages are generated.
Note. The LOG1 attribute is available on systems running J06.04 and later J-series RVUs
and H06.15 and later RVUs.
Note. If the terminal is not in the open state, iTP Secure WebServer does not log any
information and returns error 1020.