From: Steve Grubb <sgrubb@redhat.com>
To: Simon Jones <sjones@tusc.com.au>
Cc: linux-audit@redhat.com
Subject: Re: RHEL-AS-4.4 and auditd-1.0.14
Date: Wed, 14 Feb 2007 12:42:47 -0500 [thread overview]
Message-ID: <200702141242.47142.sgrubb@redhat.com> (raw)
In-Reply-To: <11541253-7ABC-440E-9E3A-229369D0F7D4@tusc.com.au>
On Tuesday 13 February 2007 18:20:04 Simon Jones wrote:
> I changed the rule from the /etc watch to individual files in the /
> etc directory and that seems to have settled it down.
>
> It seems to be a problem with watching directories only.
Hmm. The daemon doesn't make decisions at all based on what's in the event.
Offhand, I don't have any other suggestions other than a session with
valgrind. There's very little memory allocating done by the audit daemon to
make sure we do not have memory leaks.
-Steve
prev parent reply other threads:[~2007-02-14 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 4:12 RHEL-AS-4.4 and auditd-1.0.14 Simon Jones
2007-02-10 14:27 ` Steve Grubb
2007-02-12 22:54 ` Simon Jones
2007-02-13 2:33 ` Steve Grubb
2007-02-13 23:07 ` Simon Jones
2007-02-13 23:20 ` Simon Jones
2007-02-14 17:42 ` 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=200702141242.47142.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=sjones@tusc.com.au \
/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