public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Kevin Boyce <kevin.boyce@ngc.com>
To: Bill Tangren <bjt@usno.navy.mil>
Cc: linux-audit@redhat.com
Subject: Re: auditing for RHEL ES4
Date: Fri, 16 Nov 2007 11:12:53 -0500	[thread overview]
Message-ID: <1195229573.9661.12.camel@pc070168.northgrum.com> (raw)
In-Reply-To: <1195229470.9661.10.camel@pc070168.northgrum.com>


[-- Attachment #1.1: Type: text/plain, Size: 1269 bytes --]

Oops, don't forget to recompile, and then the "rpm -Uhv"

On Fri, 2007-11-16 at 11:11 -0500, Kevin Boyce wrote:

> I would download the source rpms, make your changes, change the
> version, and use the "rpm -Uhv" to upgrade existing packages.
> 
> Kevin Boyce
> Northrop Grumman Corp.
> 
> 
> On Fri, 2007-11-16 at 10:54 -0500, Bill Tangren wrote: 
> 
> > I'm running RHEL ES 4 servers, and am having difficulty with aureport. I'm
> > using audit version 1.0.15-3, the one that comes with the OS. The problem
> > is that I need daily reports, and it is not doing it. The reports always
> > cover the entire range of available logs (sometimes gigabytes of data).
> > The reports can take a LONG time to compile, and it doesn't give me the
> > daily snapshot I need. I'm thinking of installing the latest tarball and
> > compiling, as I understand more recent versions of aureport have
> > implemented time limits. [I've emailed this list before about this.]
> > 
> > My question now is, is it possible to uninstall the prepackaged audit and
> > audit-lib, and install the latest from source, without seriously hosing my
> > system?
> > 
> > TIA,
> > 
> > 
> 
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit

[-- Attachment #1.2: Type: text/html, Size: 2285 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2007-11-16 16:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16 15:54 auditing for RHEL ES4 Bill Tangren
2007-11-16 16:11 ` Kevin Boyce
2007-11-16 16:12   ` Kevin Boyce [this message]
2007-11-16 16:15     ` Bill Tangren
2007-11-16 16:24 ` Steve Grubb
2007-11-16 16:41   ` Bill Tangren
2007-12-26 21:15   ` Bill Tangren
2007-12-26 21:43     ` Steve Grubb
2007-12-26 22:03       ` Bill Tangren

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=1195229573.9661.12.camel@pc070168.northgrum.com \
    --to=kevin.boyce@ngc.com \
    --cc=bjt@usno.navy.mil \
    --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