01-03-2012
What do you mean by "reload logs"?
Usually logrotate policies are triggered with crond.
10 More Discussions You Might Find Interesting
1. Cybersecurity
I am new to the world of Unix. As part of my understanding to have a big picture of Unix, I need to understand:
1. How to review the existing unix system or audit for the settings?
2. How do I go about fixing the holes? (4 Replies)
Discussion started by: amundra
4 Replies
2. UNIX and Linux Applications
Folks
I am on a quest....
I am looking for a lightweight FTP client capable of FTPS and or SFTP that has good audit and logging capabilities without requiring a central server component. My platforms are Linux, Solaris, AIX, and Windows Server.
The kicker is I have found things that meet the... (3 Replies)
Discussion started by: ArtF
3 Replies
3. Solaris
How do i find if audit logs is secured inside Solaris 10?
· Verify that that audit log files are secured and owned appropriately.
this is the question (1 Reply)
Discussion started by: werbotim
1 Replies
4. AIX
Dear All
When I start the AIX(6100-06)audit subsystem.
the log will save in /audit/stream.out (or /audit/trail), but in default when /audit/stream.out to grow up to 150MB.
It will replace the original /audit/stream.out (or /audit/trail).
Then the /audit/stream.out become empty and... (2 Replies)
Discussion started by: nnnnnnine
2 Replies
5. Solaris
Does anyone know if there is software written to view the audit logs generated by Solaris? I am referring the the logs created by auditd. It produces an unreadable log. I am familiar with auditreduce and praudit, but I am looking for something that produces a report, much like logwatch looks at the... (4 Replies)
Discussion started by: brownwrap
4 Replies
6. Solaris
Hello all,
I've configured 'audit' service to send the audit logs to a remote log server (by using syslog plugin), which is working fine.
However, there is a problem. audit service also tries to write same information (but in binary format) in /var/audit path.
So, Is there anyway to stop... (2 Replies)
Discussion started by: Anti_Evil
2 Replies
7. Red Hat
Hello All,
I'm using a RHEL6.4 on IBM X3850 X5 server. I want to get a comprehensive report containing disk-wise health status as well as overall server status.
I see there's utility "ibm_utl_dsa_dsytd3h-9.51_portable_rhel6_x86-64.bin" which is also used to do diagnostics tasks. I'm not sure of... (1 Reply)
Discussion started by: vaibhavvsk
1 Replies
8. Solaris
HI Community,
how can i configure audit logs for global zones and standard zone. i have enabled and started auditd service and it went to maintenance mode. please help me to configure that
Thanks & Regards,
BEn (9 Replies)
Discussion started by: bentech4u
9 Replies
9. UNIX for Beginners Questions & Answers
MyLOG:
2017/11/12 17:01:54.600 : Error: LPID: 3104680848 WRONG CRITERIA FOUND. tRealBuilder::Generate
Output Required:
If Ke word "WRONG CRITERIA FOUND" in latest log ( logs are regularly generating - real time) mail to us
once mailed wait for 2 hours for second mail.
mail subject... (3 Replies)
Discussion started by: vivekn
3 Replies
10. Solaris
Hi guys.
I have to set audit logs on certain events on a solaris 10 server.
While I had no problems on linux, I'm going crazy to do the same thing on solaris 10, since I don't have enough expertise on this OS .
I should be able to identify these 4 different events:
1: Tracking all... (2 Replies)
Discussion started by: menofmayhem
2 Replies
LEARN ABOUT CENTOS
auditd
AUDITD(8) System Administration Utilities AUDITD(8)
NAME
auditd - The Linux Audit daemon
SYNOPSIS
auditd [-f] [-l] [-n] [-s disable|enable|nochange]
DESCRIPTION
auditd is the userspace component to the Linux Auditing System. It's responsible for writing audit records to the disk. Viewing the logs is
done with the ausearch or aureport utilities. Configuring the audit rules is done with the auditctl utility. During startup, the rules in
/etc/audit/audit.rules are read by auditctl and loaded into the kernel. Alterately, there is also an augenrules program that reads rules
located in /etc/audit/rules.d/ and compiles them into an audit.rules file. The audit daemon itself has some configuration options that the
admin may wish to customize. They are found in the auditd.conf file.
OPTIONS
-f leave the audit daemon in the foreground for debugging. Messages also go to stderr rather than the audit log.
-l allow the audit daemon to follow symlinks for config files.
-n no fork. This is useful for running off of inittab or systemd.
-s=ENABLE_STATE
specify when starting if auditd should change the current value for the kernel enabled flag. Valid values for ENABLE_STATE are "dis-
able", "enable" or "nochange". The default is to enable (and disable when auditd terminates). The value of the enabled flag may be
changed during the lifetime of auditd using 'auditctl -e'.
SIGNALS
SIGHUP causes auditd to reconfigure. This means that auditd re-reads the configuration file. If there are no syntax errors, it will proceed
to implement the requested changes. If the reconfigure is successful, a DAEMON_CONFIG event is recorded in the logs. If not success-
ful, error handling is controlled by space_left_action, admin_space_left_action, disk_full_action, and disk_error_action parameters
in auditd.conf.
SIGTERM
caused auditd to discontinue processing audit events, write a shutdown audit event, and exit.
SIGUSR1
causes auditd to immediately rotate the logs. It will consult the max_log_size_action to see if it should keep the logs or not.
SIGUSR2
causes auditd to attempt to resume logging. This is usually needed after logging has been suspended.
FILES
/etc/audit/auditd.conf - configuration file for audit daemon
/etc/audit/audit.rules - audit rules to be loaded at startup
/etc/audit/rules.d/ - directory holding individual sets of rules to be compiled into one file by augenrules.
NOTES
A boot param of audit=1 should be added to ensure that all processes that run before the audit daemon starts is marked as auditable by the
kernel. Not doing that will make a few processes impossible to properly audit.
The audit daemon can receive audit events from other audit daemons via the audisp-remote audispd plugin. The audit daemon may be linked
with tcp_wrappers to control which machines can connect. If this is the case, you can add an entry to hosts.allow and deny.
SEE ALSO
auditd.conf(5), audispd(8), ausearch(8), aureport(8), auditctl(8), augenrules(8), audit.rules(7).
AUTHOR
Steve Grubb
Red Hat Sept 2013 AUDITD(8)