10-03-2010
No one can accurately know if the issue is related to an audit service based on (the lack of) information in your post.
Why not search the filesystem yourself and see where the big files are (and what they are)?
4 More Discussions You Might Find Interesting
1. Red Hat
Hi,
We have 200GB SAN volume mounted on Redhat EL 5. which is working fine. As my SAN supports dynamic resizing of volumes, i unmounted the volume and resized the SAN Volume to 300 GB successfully. Then i mounted again but it shows 200GB only but data is intact.
Now, my requirement is to let... (3 Replies)
Discussion started by: prvnrk
3 Replies
2. AIX
rmt0 allows get increased .. !
I have faced this issue in my AIX server, rmt0 allows get increased and it's filled /root till 100%
There is no tape in tape drive why it's increased?
Pls advice.. (1 Reply)
Discussion started by: Mr.AIX
1 Replies
3. Solaris
Hi All
After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies
4. Shell Programming and Scripting
Deal all,
I have a directory called
I want to know how many MBs are transferred to it every 2 hours.
How can I do this?
Any ideas?
I have a simple idea but I can't translate it into shell script, the idea is:
1- get the size of the folder now, using
2- then get the size of the... (4 Replies)
Discussion started by: Mohannad
4 Replies
LEARN ABOUT POSIX
audit_data
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)