From: LC Bruzenak <lenny@magitekltd.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] Add auditd listener and remote audit protocol
Date: Thu, 14 Aug 2008 19:22:24 -0500 [thread overview]
Message-ID: <1218759744.7022.272.camel@homeserver> (raw)
In-Reply-To: <200808142007.02746.sgrubb@redhat.com>
On Thu, 2008-08-14 at 20:07 -0400, Steve Grubb wrote:
> On Thursday 14 August 2008 19:50:23 LC Bruzenak wrote:
> > I cannot speak for other end-users...but my guess is that if they are
> > using audit and aggregating they probably care about not dropping it,
> > whereas others can just syslog the events if the auditd isn't enabled
> > and then use centralized syslog, right?
>
> Does syslog queue unsent messages and recover them?
>
> -Steve
Not AFAIK...but then again it isn't configurable to panic the machine on
failure.
I think you have a good point - this is the first cut and maybe later on
institute a "replay daemon" or something which can send events on
reconnect.
We will not lose them locally so that's covered. After that it is a
different problem.
Thx,
LCB.
--
LC (Lenny) Bruzenak
lenny@magitekltd.com
next prev parent reply other threads:[~2008-08-15 0:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 21:43 [PATCH] Add auditd listener and remote audit protocol DJ Delorie
2008-08-14 21:58 ` LC Bruzenak
2008-08-14 22:16 ` DJ Delorie
2008-08-14 23:00 ` John Dennis
2008-08-14 23:02 ` LC Bruzenak
2008-08-14 23:16 ` John Dennis
2008-08-14 23:55 ` Steve Grubb
2008-08-14 23:16 ` DJ Delorie
2008-08-14 23:26 ` LC Bruzenak
2008-08-14 23:37 ` John Dennis
2008-08-14 23:50 ` LC Bruzenak
2008-08-15 0:07 ` Steve Grubb
2008-08-15 0:22 ` LC Bruzenak [this message]
2008-08-15 0:27 ` Steve Grubb
2008-08-15 0:31 ` LC Bruzenak
2008-08-15 0:36 ` DJ Delorie
2008-08-15 0:41 ` LC Bruzenak
2009-09-29 17:52 ` LC Bruzenak
2009-09-29 18:51 ` Norman Mark St. Laurent
2009-09-29 19:14 ` LC Bruzenak
2009-09-29 19:27 ` Steve Grubb
2008-08-15 0:23 ` DJ Delorie
2008-08-15 0:04 ` Steve Grubb
2008-08-15 0:19 ` DJ Delorie
2008-08-15 0:23 ` Steve Grubb
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=1218759744.7022.272.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 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.