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

Table Of Contents
value The input pointer points to the content of the value for non-scalar types of
data. You must copy the contents that are of value. The memory for the value
must not be freed after you copy the contents. The input pointer points to
NULL if the client uses an IPv4 address and the user input argument is
AUTH_CLIENT_IPADDRV6. The input pointer also points to NULL if the client
uses an IPv6 address and the user input argument is
SDK_AUTH_CLIENT_IPADDRV4.
Return
Returns one of the following values:
SDK_SUCCESS if the operation succeeds.
SDK_INVALID_ARG if the arguments are invalid.
Logging APIs
This section discusses the APIs that can be used to customize the logging functionality
of the HP-UX AAA Server.
NOTE: The HP-UX AAA Server supports two logging subsystems that are used
simultaneously. There is a standard logging subsystem that can be directed to a AAA
log file, stdout, or syslog, and a debug log file that can be used for troubleshooting
and debugging.
int sdk_logit()
int sdk_logit ( int level, const char *format, /* [arg,], */
...)
Usage
Logs the provided log message to the logging facility specified while starting the HP-UX
AAA Server. It can be one of the HP-UX AAA log files, syslog or stdout. By default,
log messages are logged in the HP-UX AAA log files (the /var/opt/aaa/logs/
directory is the default location).
Input
level
Log level from syslog.h. You can use one of the following log levels from
/usr/include/syslog.h:
Use LOG_EMERG if the system is unusable
Use LOG_ALERT if action must be taken immediately
Use LOG_CRIT for critical conditions
Use LOG_ERR for error conditions
Use LOG_WARNING for warning conditions
Use LOG_NOTICE for normal but signification conditions
Use LOG_INFO for informational conditions
APIs in the HP-UX AAA Server SDK 587