From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Audit config for NISPOM req's Date: Fri, 22 Dec 2006 11:25:46 -0500 Message-ID: <200612221125.46619.sgrubb@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: "Wieprecht, Karen M." Cc: "Curtas, Anthony R." , linux-audit@redhat.com List-Id: linux-audit@redhat.com On Friday 22 December 2006 11:22, Wieprecht, Karen M. wrote: > So you still need a watch on the file in order to collect get audit events > to be generated in the event of file access failures, is that correct? That entirely depends on the rule. If you are using possible, yes. If your rules are always/never or a watch then you should be ok. -Steve