public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: "Norman Mark St. Laurent" <mstlaurent@conceras.com>
To: LC Bruzenak <lenny@magitekltd.com>
Cc: linux-audit@redhat.com
Subject: Re: buffer space
Date: Mon, 17 Aug 2009 14:46:30 -0400	[thread overview]
Message-ID: <4A89A586.9020008@conceras.com> (raw)
In-Reply-To: <1250532894.3048.729.camel@homeserver>

Depending if you are using logrotate.d/audit  and how it numbers the 
files as it rotates... 

audit.log.1.gz
audit.log.2.gz
...
audit.log.89.gz
audit.log.90.gz

The sort below will but the list in exact order....

zcat `ls /var/log/audit/*.gz | sort -t. --key=3,2n` | ausearch -i

Thank u Steve...

Norman Mark St. Laurent
Conceras | Chief Technology Officer and ISSE

Web:  http://www.conceras.com

Connect. Collaborate. Conceras.



LC Bruzenak wrote:
> On Mon, 2009-08-17 at 14:01 -0400, Steve Grubb wrote:
>   
>>> It's a problem for me too.
>>> I was thinking about just patching the ausearch code to behave as
>>> desired...but hoping Steve beat me to it so there was a greatly
>>>       
>> reduced
>>     
>>> chance of bad code...
>>>       
>> #cat `ls /var/log/audit/a* | sort -r` | ausearch -i
>> #cat `ls /var/log/audit/a* | sort -r` | aureport
>>
>> cat can open more than one file at a time,
>>
>> -Steve
>>     
>
> Told you so!
> :)
>
> LCB.
>
>   

  reply	other threads:[~2009-08-17 18:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 14:56 buffer space David Flatley
2009-08-13 15:29 ` Matthew Booth
2009-08-13 18:28 ` Steve Grubb
2009-08-17 14:49   ` David Flatley
2009-08-17 15:07     ` Steve Grubb
2009-08-17 15:36       ` Norman Mark St. Laurent
2009-08-17 16:38       ` David Flatley
2009-08-17 16:52         ` LC Bruzenak
2009-08-17 17:06           ` David Flatley
2009-08-17 17:15             ` LC Bruzenak
2009-08-17 17:24               ` LC Bruzenak
2009-08-17 21:18                 ` David Flatley
2009-08-17 17:32               ` David Flatley
2009-08-17 17:46                 ` LC Bruzenak
2009-08-17 18:01                   ` Steve Grubb
2009-08-17 18:13                     ` Norman Mark St. Laurent
2009-08-17 18:14                     ` LC Bruzenak
2009-08-17 18:46                       ` Norman Mark St. Laurent [this message]
2009-08-17 19:37                         ` Steve Grubb
2009-08-17 19:46                           ` Norman Mark St. Laurent
2009-08-18 13:02                           ` David Flatley
2009-08-18 15:09                             ` LC Bruzenak
2009-08-18 15:53                               ` Steve Grubb
2009-08-27 17:21                           ` David Flatley
2009-08-27 17:32                             ` Steve Grubb
2009-08-27 17:45                               ` David Flatley
2009-08-27 18:45                                 ` Steve Grubb
2009-08-27 17:33                             ` LC Bruzenak
2009-08-23  4:12       ` D.A. Muran-de Assereto
2009-08-17 15:34     ` Norman Mark St. Laurent
2009-08-17 16:58       ` Mike Nixon
2009-08-23  4:32         ` David Muran-de Assereto
2009-08-23 16:12           ` Mike Nixon
2009-08-23 20:24             ` David Muran-de Assereto

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=4A89A586.9020008@conceras.com \
    --to=mstlaurent@conceras.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