From: LC Bruzenak <lenny@magitekltd.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: Near Term Audit Road Map
Date: Fri, 27 Feb 2009 10:23:16 -0600 [thread overview]
Message-ID: <1235751796.7212.26.camel@homeserver> (raw)
In-Reply-To: <1235751224.7212.24.camel@homeserver>
On Fri, 2009-02-27 at 10:13 -0600, LC Bruzenak wrote:
> On Fri, 2009-02-27 at 10:33 -0500, Steve Grubb wrote:
> > ...
> audispd was separate was to allow it to deal with the vagaries of
> endpoint and delivery issues while the auditd kept doing its thing.
Maybe the dispatchers themselves are still separate.
LCB.
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
next prev parent reply other threads:[~2009-02-27 16:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 15:33 Near Term Audit Road Map Steve Grubb
2009-02-27 16:13 ` LC Bruzenak
2009-02-27 16:23 ` LC Bruzenak [this message]
2009-02-27 16:56 ` Steve Grubb
2009-03-24 16:29 ` audisp-remote and audisp-prelude question LC Bruzenak
2009-03-24 16:41 ` Steve Grubb
2009-03-24 16:55 ` Sebastien Tricaud
2009-03-24 17:30 ` LC Bruzenak
2009-03-24 17:06 ` Steve Grubb
2009-03-24 18:01 ` LC Bruzenak
2009-03-24 18:13 ` Steve Grubb
2009-02-27 20:59 ` Near Term Audit Road Map Matthew Booth
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=1235751796.7212.26.camel@homeserver \
--to=lenny@magitekltd.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@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