From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steve Grubb <sgrubb@redhat.com>
Subject: Re: audit 2.3.6 released
Date: Wed, 23 Apr 2014 14:51:45 -0400
Message-ID: <53785049.dfgRrcZIXE@x2>
References: <1517873.WD6C24XtlD@x2> <1853896.aYEMLF8qDN@x2>
	<1397786904.2800.15.camel@swtf.swtf.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <linux-audit-bounces@redhat.com>
In-Reply-To: <1397786904.2800.15.camel@swtf.swtf.dyndns.org>
List-Unsubscribe: <https://www.redhat.com/mailman/options/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/linux-audit>
List-Post: <mailto:linux-audit@redhat.com>
List-Help: <mailto:linux-audit-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=subscribe>
Sender: linux-audit-bounces@redhat.com
Errors-To: linux-audit-bounces@redhat.com
To: burn@swtf.dyndns.org
Cc: linux audit <linux-audit@redhat.com>
List-Id: linux-audit@redhat.com

On Friday, April 18, 2014 12:08:24 PM Burn Alting wrote:
> Please find attached a patch against 2.3.6 that, when checkpointing,
> notices if we identify an audit.log file to use (ie the dev and inode
> match) but we find a complete event whose time is > 2 seconds past the
> checkpoint time. This should not happen, as the checkpoint event should
> be found BEFORE any other complete event for the checkpoint event was
> the last displayed complete event in the file. When this occurs, a
> message is printed to stderr and ausearch will terminate with an exit
> code of 12.
> 
> This typically occurs if there is a lot of processing or a long time
> occurs between  two invocations of ausearch --checkpoint. Basically, an
> inode is reused in one of the new audit.log files.

Thanks for the patch. Applied as commit 950 with a couple formatting changes.

-Steve