public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: LC Bruzenak <lenny@magitekltd.com>
Cc: linux-audit@redhat.com
Subject: Re: ausearch on aggregation - syscall difference
Date: Fri, 24 Oct 2008 14:37:18 -0400	[thread overview]
Message-ID: <200810241437.18458.sgrubb@redhat.com> (raw)
In-Reply-To: <1224869269.9388.19.camel@homeserver>

On Friday 24 October 2008 13:27:49 LC Bruzenak wrote:
> So it looks like the architectures interpretation (-i) of the syscall is
> where it differs?

Yes, there was a collision between the unset value and the i386 value in the 
source code. This meant that it when it ran across I386 machines, it thought 
there was an error looking it up and reverted to looking up the uname machine 
value as a fallback.  Svn commit 155 fixes this.

-Steve

  reply	other threads:[~2008-10-24 18:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 17:08 ausearch on aggregation - syscall difference LC Bruzenak
2008-10-24 17:16 ` Steve Grubb
2008-10-24 17:27   ` LC Bruzenak
2008-10-24 18:37     ` Steve Grubb [this message]
2008-10-24 17:30   ` LC Bruzenak
2008-10-24 18:28 ` John Dennis
2008-10-24 18:38   ` LC Bruzenak

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=200810241437.18458.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=lenny@magitekltd.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