From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Using audit for service monitoring... Date: Thu, 28 Sep 2006 16:46:46 -0400 Message-ID: <200609281646.46095.sgrubb@redhat.com> References: <20060928160020.D6AB3732D6@hormel.redhat.com> <1159475357.30605.16.camel@bofh.arlut.utexas.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1159475357.30605.16.camel@bofh.arlut.utexas.edu> 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: linux-audit@redhat.com, Randy Zagar List-Id: linux-audit@redhat.com On Thursday 28 September 2006 16:29, Randy Zagar wrote: > More importantly, is this an appropriate use of the audit subsystem, or > should I be doing this some other way? Generally, the audit system is used for logging security relevant artifac= ts.=20 But its been used for bootup readahead analysis, too. So, you could use i= t=20 for this, but you might get more data than you want. Try it and see. > If this is the right way to do it, how can I easily determine which > syscalls can return ESTALE? =C2=A0Using '-S all' seems wasteful... Maybe you can try "auditctl -a exit,always -F perm=3Dall -F exit=3D-13" perm selects filesystem classes of syscalls. -Steve