Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #412
Difficulty: Medium
AT&T 3B computer systems included the 3B2, 3B5, 3B15, 3B20S, and 3B4000. These computers were named after the successful 3B20D. The 3B20S (simplex) ran using the UNIX operating system and was developed at Bell Labs and produced by WECo in 1982 for the general purpose internal Bell System use, and later the mini-computer market.
True or False?
Linux & Unix Commands - Search Man Pages

audit_data(4) [bsd man page]

audit_data(4)							   File Formats 						     audit_data(4)

NAME
audit_data - current information on audit daemon SYNOPSIS
/etc/security/audit_data DESCRIPTION
The audit_data file contains information about the audit daemon. The file contains the process ID of the audit daemon, and the pathname of the current audit log file. The format of the file is: pid>:<pathname> Where pid is the process ID for the audit daemon, and pathname is the full pathname for the current audit log file. EXAMPLES
Example 1: A sample audit_data file. 64:/etc/security/audit/server1/19930506081249.19930506230945.bongos FILES
/etc/security/audit_data ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Obsolete | +-----------------------------+-----------------------------+ SEE ALSO
audit(1M), auditd(1M), bsmconv(1M), audit(2), audit_control(4), audit.log(4) NOTES
The functionality described on this manual page is internal to audit(1M) and might not be supported in a future release. The auditd utility is the only supported mechanism to communicate with auditd(1M). The current audit log can be determined by examining the configured audit directories. See audit_control(4). The functionality described on this manual page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for more information. SunOS 5.10 14 Nov 2002 audit_data(4)

Check Out this Related Man Page

auditd(1M)                                                System Administration Commands                                                auditd(1M)

NAME
auditd - audit daemon SYNOPSIS
/usr/sbin/auditd DESCRIPTION
The audit daemon, auditd, controls the generation and location of audit trail files and the generation of syslog messages based on the def- initions in audit_control(4). If auditing is enabled, auditd reads the audit_control(4) file to do the following: o reads the path to a library module for realtime conversion of audit data into syslog messages; o reads other parameters specific to the selected plugin or plugins; o obtains a list of directories into which audit files can be written; o obtains the percentage limit for how much space to reserve on each filesystem before changing to the next directory. audit(1M) is used to control auditd. It can cause auditd to: o close the current audit file and open a new one; o close the current audit file, re-read /etc/security/audit_control and open a new audit file; o close the audit trail and terminate auditing. Auditing Conditions The audit daemon invokes the program audit_warn(1M) under the following conditions with the indicated options: audit_warn soft pathname The file system upon which pathname resides has exceeded the minimum free space limit defined in audit_control(4). A new audit trail has been opened on another file system. audit_warn allsoft All available file systems have been filled beyond the minimum free space limit. A new audit trail has been opened anyway. audit_warn hard pathname The file system upon which pathname resides has filled or for some reason become unavailable. A new audit trail has been opened on another file system. audit_warn allhard count All available file systems have been filled or for some reason become unavailable. The audit daemon will repeat this call to audit_warn every twenty seconds until space becomes available. count is the number of times that audit_warn has been called since the problem arose. audit_warn ebusy There is already an audit daemon running. audit_warn tmpfile The file /etc/security/audit/audit_tmp exists, indicating a fatal error. audit_warn nostart The internal system audit condition is AUC_FCHDONE. Auditing cannot be started without rebooting the system. audit_warn auditoff The internal system audit condition has been changed to not be AUC_AUDITING by someone other than the audit daemon. This causes the audit daemon to exit. audit_warn postsigterm An error occurred during the orderly shutdown of the auditing system. audit_warn getacdir There is a problem getting the directory list from /etc/security/audit/audit_control. The audit daemon will hang in a sleep loop until this file is fixed. FILES
/etc/security/audit/audit_control /etc/security/audit/audit_data ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
audit(1M), audit_warn(1M), bsmconv(1M), praudit(1M), auditon(2), auditsvc(2), audit.log(4), audit_control(4), audit_data(4), attributes(5) NOTES
The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for more information. auditd is loaded in the global zone at boot time if auditing is enabled. See bsmconv(1M). If the audit policy perzone is set, auditd runs in each zone, starting automatically when the local zone boots. If a zone is running when the perzone policy is set, auditing must be started manually in local zones. It is not necessary to reboot the system or the local zone to start auditing in a local zone. auditd can be started with "/usr/sbin/audit -s" and will start automatically with future boots of the zone. When auditd runs in a local zone, the configuration is taken from the local zone's /etc/security directory's files: audit_control, audit_class, audit_user, audit_startup, and audit_event. SunOS 5.10 26 May 2004 auditd(1M)

Featured Tech Videos