Re: buffer space

Thanks Steve! If I were to move all the rotated logs to another directory, say /home/logs. So instead of doing "ausearch -i" to capture all the information in the rotated logs in /var/log/audit directory. I would do "ausearch -i -f /home/logs" , correct? Backlog is set to 12288 right now. The SECSCAN requires many -w (watches) and a fair amount of syscalls. I modified the syscalls to add your recommendation for using "arch=b32" and "arch=b64". Because I was getting errors restarting the auditd on some of their recommendations one of which was mount? Another setting I believe was doing me in was the log size is 20 megs and I allow 8 rotated logs. But I had admin_disk_full set to 160 and the action was suspend. So this could have been tripping me up also. I would like to be able to do the audit log extractions (ausearch and aureport) when I get say 8 - 20 megs logs. I see I can do an exec on a script in max_log_file_action. So if I set the max_log_file to 160, I can then run a script to move the rotated logs and process them, thus not stopping auditd and keeping things working? I would set the max rotated logs to 10 to allow the new rotated log space then move the logs as you suggest. Thanks. David Flatley CISSP From: Steve Grubb <sgrubb(a)redhat.com&gt; To: linux-audit(a)redhat.com Cc: David Flatley/Burlington/IBM@IBMUS Date: 08/13/2009 02:29 PM Subject: Re: buffer space On Thursday 13 August 2009 10:56:50 am David Flatley wrote: have I would be curious what the SECSCAN recommendations are. Never heard of it... I think this is your problem. If you have audit rules loaded and stop auditd, then audit events are going to pile up in the queue waiting for auditd to download them. At some point the kernel will decide auditd doesn't exist and will dump all events to syslog. This probably is not what you want either. I would recommend calling "service auditd rotate" and then grab logs audit.log.1 -> audit.logs.7 and move them away to another directory for post processing the contents. You may also want to check you backlog size settings too. cron Shouldn't really make a difference. -Steve