From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: "Boyce, Kevin P. (Melbourne, FL)" <Kevin.Boyce@ngc.com>
Subject: Re: Audit-1.0.14
Date: Wed, 11 Oct 2006 08:24:37 -0400 [thread overview]
Message-ID: <200610110824.38005.sgrubb@redhat.com> (raw)
In-Reply-To: <04485C8018722949A3DF79E193BB44DB07A50599@xcgfl107.northgrum.com>
On Wednesday 11 October 2006 07:49, Boyce, Kevin P. (Melbourne, FL) wrote:
> I can install the deb files and the audit daemon runs, but it has trouble
> parsing the audit.rules file. The error I am getting is "Error sending
> insert watch request (Invalid Argument)."
This is not a parsing error...its worse. The audit 1.0.x series was developed
to compliment the RHEL4 kernel. At the time, it was envisioned that the
technique used for watches would be accepted upstream. It was rejected due to
some overlap with inotify, so the watch system was re-written. The audit
1.2.x series has the code for the new system. Watches were not accepted
upstream until the 2.6.18 kernel.
> I have a requirement to use these two kernel versions, and unfortunately
> can't use redhat, fedora, or their kernel binaries.
They you are limited to inode based auditing. Or maybe if you put the things
you have to watch onto one partition, you can use devmajor and minor. I'd try
to move to a 2.6.18 kernel with the latest audit package.
-Steve
next prev parent reply other threads:[~2006-10-11 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 11:49 Audit-1.0.14 Boyce, Kevin P. (Melbourne, FL)
2006-10-11 12:24 ` Steve Grubb [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-09 19:56 Audit-1.0.14 Todd, Charles
2006-11-13 14:19 ` Audit-1.0.14 Steve Grubb
2006-11-14 4:17 ` Audit-1.0.14 Todd, Charles
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=200610110824.38005.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=Kevin.Boyce@ngc.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