From: Valdis.Kletnieks@vt.edu
To: Aaron Lippold <lippold@gmail.com>
Cc: linux-audit@redhat.com
Subject: Re: Filesystem filling up ...
Date: Fri, 29 Jun 2007 11:39:29 -0400 [thread overview]
Message-ID: <8178.1183131569@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 27 Jun 2007 19:42:39 +0200." <39d2723b0706271042y2885144dj29e7da8adc90e630@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 848 bytes --]
On Wed, 27 Jun 2007 19:42:39 +0200, Aaron Lippold said:
> # Audit Failed opens
> -a exit,always -S open -F success!=0
Note that a *lot* of programs will attempt to open optional config files,
and happily go on their merry way when they get an -ENOENT leaving an audit
entry for you to drown in. I just tested the venerable 'xfontsel', and at
one point, it generated *12* -ENOENT in a row looking for a bitmap for
a cursor before finding one it liked. The next 3 cursors only needed
9, 10, and 8 failed attempts before it found one.
> # Audit success and failure of delete
> -a exit,always -S unlink -S rmdir
That's going to be really painful on any system that does software development,
as your average compile generates a lot of temporary files that get unlinked.
You may want to investigate whether it's feasible to ignore unlinks in /tmp.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 226 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2007-06-29 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 17:42 Filesystem filling up Aaron Lippold
2007-06-27 18:17 ` Stephen John Smoogen
2007-06-29 15:39 ` Valdis.Kletnieks [this message]
2007-07-03 21:13 ` Steve Grubb
2007-07-07 20:42 ` Aaron Lippold
2007-07-08 20:17 ` Steve Grubb
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=8178.1183131569@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-audit@redhat.com \
--cc=lippold@gmail.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