Re: Patch to auparse to handle out of order messages 2 of 3
Noted .. old habits ... I've always ifdef'd new code effecting a core
element of a capability and remove it a release or two later.
On Wed, 2016-01-06 at 10:45 -0500, Steve Grubb wrote:
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