From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Timothy R. Chavez" Subject: Re: Logging failed open() calls on /var/log/audit/audit.log Date: Tue, 27 Jun 2006 16:32:46 -0500 Message-ID: <1151443966.6863.18.camel@localhost.localdomain> References: <20060627211553.GA11601@zk3.dec.com> <200606271721.05626.sgrubb@redhat.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200606271721.05626.sgrubb@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: Steve Grubb Cc: linux-audit@redhat.com List-Id: linux-audit@redhat.com On Tue, 2006-06-27 at 17:21 -0400, Steve Grubb wrote: > On Tuesday 27 June 2006 17:15, Amy Griffis wrote: > > If you would like to see a record in this case, you must add a watch > > for /var/log/audit. > > I don't see a record watching this either. > > -Steve Maybe because you're executing in the system-call attempting the access of audit.log and it's in this context the permissions to do so are checked. Been awhile, but looking at fs/open.c:do_sys_open, should there be an fsnotify_open() hook in the error path as well? -tim