All of lore.kernel.org
 help / color / mirror / Atom feed
From: LC Bruzenak <lenny@magitekltd.com>
To: "Pittigher, Raymond - ES" <Raymond.Pittigher@itt.com>
Cc: "linux-audit@redhat.com" <linux-audit@redhat.com>
Subject: Re: log files
Date: Fri, 17 Jun 2011 14:56:24 -0500	[thread overview]
Message-ID: <1308340584.7213.50.camel@lcb> (raw)
In-Reply-To: <4DFBA7C2.8070000@itt.com>

On Fri, 2011-06-17 at 15:15 -0400, Pittigher, Raymond - ES wrote:
> 
> The plan would be to rotate the log at midnight Saturday, use the
> aureport to read the file and give it some kind of format, dump the data
> into a mysql database, then parse it with php on a apache server with a
> firefox front end. Or something like that. 

OK; that was my thinking as well.
Only I roll mine up each day already and move them out of the way.

I think you would likely use a custom program which used the parse libs
to extract the searchable elements from each event.

What I was wondering is if on the front end (cgi+browser-side) you had
something in mind which existed already - or if you would code it up
from scratch with the php-mysql piece?

Thx,
LCB

-- 
LC (Lenny) Bruzenak
lenny@magitekltd.com

  reply	other threads:[~2011-06-17 19:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17 18:15 log files Pittigher, Raymond - ES
2011-06-17 18:27 ` LC Bruzenak
2011-06-17 18:32   ` Pittigher, Raymond - ES
2011-06-17 18:57     ` Dominick Grift
     [not found]     ` <1308337014.7213.10.camel@lcb>
2011-06-17 19:15       ` Pittigher, Raymond - ES
2011-06-17 19:56         ` LC Bruzenak [this message]
2011-06-17 21:33           ` Pittigher, Raymond - ES
2011-06-17 18:38 ` Steve Grubb
  -- strict thread matches above, loose matches on Subject: below --
2004-06-17  7:48 Log Files Patrick Nelson
2004-06-17  7:55 ` Marc Haber
2003-07-03  6:13 Log files Steven Mugassa

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=1308340584.7213.50.camel@lcb \
    --to=lenny@magitekltd.com \
    --cc=Raymond.Pittigher@itt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.