audit_log(9) [suse man page]

AUDIT_LOG(9)							 Audit Interfaces						      AUDIT_LOG(9)

NAME

       audit_log - Log an audit record

SYNOPSIS

       void audit_log(struct audit_context * ctx, gfp_t gfp_mask, int type, const char * fmt, ...);

ARGUMENTS

       ctx
	   audit context

       gfp_mask
	   type of allocation

       type
	   audit message type

       fmt
	   format string to use @...: variable parameters matching the format string

       ...
	   variable arguments

DESCRIPTION

       This is a convenience function that calls audit_log_start, audit_log_vformat, and audit_log_end. It may be called in any context.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010							      AUDIT_LOG(9)

audit(4)						     Kernel Interfaces Manual							  audit(4)

NAME

       audit - audit trail format and other information for auditing

DESCRIPTION

       Audit  records  are  generated  when  users  make security-relevant system calls, as well as by self-auditing processes that call (see aud-
       write(2)).  Access to the auditing system is restricted to super-user.

       Each audit record consists of an audit record header and a record body.	The record header is comprised of  sequence  number,  process  ID,
       event  type,  and record body length.  The sequence number gives relative order of all records; the process ID belongs to the process being
       audited; the event type is a field identifying the type of audited activity; the length is the record body length expressed in bytes.

       The record body is the variable-length component of an audit record containing more information about the audited  activity.   For  records
       generated  by  system calls, the body contains the time the audited event completes in either success or failure, and the parameters of the
       system calls; for records generated by self-auditing processes, the body consists of the time audwrite(2) writes the records and the  high-
       level description of the event (see audwrite(2)).

       The  records  in  the audit trail are compressed to save file space.  When a process is audited the first time, a pid identification record
       (PIR) is written into the audit trail containing information that remains constant throughout the lifetime of the process.   This  includes
       the  parent's process ID, audit tag, real user ID, real group ID, effective user ID, effective group ID, group ID list, effective,  permit-
       ted, and retained privileges, compartment ID, and the terminal ID (tty).  The PIR is entered only once per process per audit trail.

       Information accumulated in an audit trail is analyzed and displayed by (see audisp(1M)).

AUTHOR

       was developed by HP.

SEE ALSO

       audsys(1M), audevent(1M), audisp(1M), audomon(1M), audwrite(2), audit(5), compartments(5), privileges(5).

																	  audit(4)