Main index | Section 3 | Options |
#include <bsm/libbsm.h>
The au_get_state() function provides a lightweight way to check whether or not auditing is enabled. If a client wants to use this function to determine whether an entire series of audit calls should be made -- as in the common case of a caller building a set of tokens, then writing them -- it should cache the audit status in a local variable. This function always returns the current state of auditing. If audit notification has not already been initialized by calling au_notify_initialize() it will be automatically initialized on the first call of this function.
The au_notify_initialize() function initializes audit notification.
The au_notify_terminate() function cancels audit notification and frees the resources associated with it. Responsible code that no longer needs to use au_get_state() should call this function.
The au_notify_initialize() function returns 0 on success, AU_UNIMPL if audit does not appear to be supported by the system, or one of the status codes defined in <notify.h> on Mac OS X to indicate the error.
The au_notify_terminate() function returns 0 on success, or -1 on failure.
The Basic Security Module (BSM) interface to audit records and audit event stream format were defined by Sun Microsystems.
AU_NOTIFY (3) | July 29, 2015 |
Main index | Section 3 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
“ | A typical Unix /bin or /usr/bin directory contains a hundred different kinds of programs, written by dozens of egotistical programmers, each with its own syntax, operating paradigm, rules of use ... strategies for specifying options, and different sets of constraints. | ” |
— The Unix Haters' handbook |