HP-UX AAA Server A.08.01 administrator's guide (T1428-90072, May 2010)

NOTE: Event names are case-insensitive (MyEvent is considered identical with
MYEVENT).
Operation
The exit command terminates the evaluation of the policy and returns the named
event to the FSM. The use of an undefined event name results in an undefined-event
load-time error.
The log Command
Syntax
log "<log-level>" "<log-message>”
log "<log-level>" "<log-message>”, <attr-spec>
log "<log-level>" "<log-message>”, <attr-spec>, <attr-spec>, ...<attr-spec>
Parameters
• <log-level>: The <log-level> parameter must be a quoted string and a log-level type.
Following are the valid log levels:
— ERROR
— CRITICAL
— ALERT
— WARNING
— INFO
NOTE: The <log-level> parameter is case-insensitive. For example, ERROR is
considered identical with Error.
• <log-message>: The <log-message> parameter must be a quoted string. You can use
multiple instances of <attr-spec> and cause all named instances to be reported in
the log file. For more information on attribute specifications, see “Attribute
Specifications” (page 422). If <attr-spec> refers to an instance that is not present, this
is indicated in the log file output.
Operation
Executing the log command results in a message being written to the log file. When
attributes are specified, they are appended to the log message. All log output lines
include the name of the decision file and the line location of the log command that
generated the message. All log output is generated using the standard logging functions
that prepend a timestamp to the output line.
Defining a Policy in a Decision File 419