From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com, Randy Zagar <zagar@arlut.utexas.edu>
Subject: Re: Using audit for service monitoring...
Date: Thu, 28 Sep 2006 16:46:46 -0400 [thread overview]
Message-ID: <200609281646.46095.sgrubb@redhat.com> (raw)
In-Reply-To: <1159475357.30605.16.camel@bofh.arlut.utexas.edu>
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 artifacts.
But its been used for bootup readahead analysis, too. So, you could use it
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? Using '-S all' seems wasteful...
Maybe you can try "auditctl -a exit,always -F perm=all -F exit=-13"
perm selects filesystem classes of syscalls.
-Steve
prev parent reply other threads:[~2006-09-28 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060928160020.D6AB3732D6@hormel.redhat.com>
2006-09-28 20:29 ` Using audit for service monitoring Randy Zagar
2006-09-28 20:46 ` Steve Grubb [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200609281646.46095.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=zagar@arlut.utexas.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.