linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com, burn@swtf.dyndns.org
Subject: Re: Patch to auparse to handle out of order messages 2 of 3
Date: Wed, 06 Jan 2016 10:45:44 -0500	[thread overview]
Message-ID: <3311155.vSfdxMiWeB@x2> (raw)
In-Reply-To: <1452076194.26850.88.camel@swtf.swtf.dyndns.org>

On Wednesday, January 06, 2016 09:29:54 PM Burn Alting wrote:
> #2 - the 'lol' patch itself. Integrate the ausearch/aureport 'lol' code
> into auparse() and adjust auparse() to deal with maintain an incore list
> of incomplete events.

Quick question...there is this:

#define        LOL_EVENTS      1

Couldn't we just assume that this is desired and get rid of all the #ifdefs? 
(You don't need to re-send the patch.) Ideally I would like everyone running 
the same code for support purposes.

-Steve

  reply	other threads:[~2016-01-06 15:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 10:29 Patch to auparse to handle out of order messages 2 of 3 Burn Alting
2016-01-06 15:45 ` Steve Grubb [this message]
2016-01-06 21:24   ` Burn Alting
2016-01-06 23:40     ` 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=3311155.vSfdxMiWeB@x2 \
    --to=sgrubb@redhat.com \
    --cc=burn@swtf.dyndns.org \
    --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;
as well as URLs for NNTP newsgroup(s).