From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: expected performance hit for logging all execve's?
Date: Fri, 20 Jan 2012 19:29:14 -0500 [thread overview]
Message-ID: <201201201929.14578.sgrubb@redhat.com> (raw)
In-Reply-To: <CALnj_=5g2Z3cWqvsyzYW-CGriJZRKo9S68QgThyLwYqvVtL8=g@mail.gmail.com>
On Friday, January 20, 2012 03:06:13 PM Peter Moody wrote:
> I'm trying to run some tests so I can find locally relevant numbers,
> but I was wondering if you had any idea what sort of performance hit
> I'd be incurring by logging every successful execve.
>
> To be sure, I consider this a bad idea and I'm actually looking to
> disuade people of it.
It is a bad idea. Think of shell scripting.You can get 100s of execve's for just
one command on a command line. You'll never find what you think you wanted. I
think we did some testing over 5 years ago. There was a micro-benchmark here:
http://people.redhat.com/sgrubb/files/lspp-perf.tar.gz
I think it was testing the access syscall. But you can substitute what you want.
I have not benchmarked the audit system in years.
-Steve
prev parent reply other threads:[~2012-01-21 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 20:06 expected performance hit for logging all execve's? Peter Moody
2012-01-21 0:29 ` 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=201201201929.14578.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox