From: LC Bruzenak <lenny@magitekltd.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: audit-1.7.16 released
Date: Tue, 17 Nov 2009 22:16:35 -0600 [thread overview]
Message-ID: <cecd18b00911172016n46ae1014wf1de81c395e5f6cd@mail.gmail.com> (raw)
In-Reply-To: <cecd18b00911171952w4b25fdcah9aece5c86dc126e0@mail.gmail.com>
On Tue, Nov 17, 2009 at 9:52 PM, LC Bruzenak <lenny@magitekltd.com> wrote:
> On Tue, Nov 17, 2009 at 3:48 PM, Steve Grubb <sgrubb@redhat.com> wrote:
>> On Monday 16 November 2009 06:52:24 pm LC Bruzenak wrote:
>>> > You should have daemon start/end events at the aggregator. Are they not
>>> > getting there? Also, the aggregator should have matching
>>> > connect/disconnect events.
>>>
>>> I am not getting the DAEMON_END events. In an orderly shutdown, the
>>> network shuts down before the audit daemon does.
>>
>> OK, I'll take a look to see if things can be reordered to let this event get
>> sent.
>>
>> -Steve
>>
>
> Thanks, that would help in the case where the client shuts down normally.
> There is definitely utility in having a positive event come from the
> sender saying it is shutting down.
>
> But if the client gets the power cord yanked out it doesn't help me,
> so I'll still try to add something on the server side to add a local
> audit event as well as the syslog.
>
OK, I see it appears it would work as expected.
I see that the "close_client" gets called on a client timeout, and it
does send a AUDIT_DAEMON_CLOSE event. I will test that ASAP.
I assume a client which just drops off would hit this case.
Thx!
LCB.
--
LC (Lenny) Bruzenak
prev parent reply other threads:[~2009-11-18 4:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 15:55 audit-1.7.16 released Steve Grubb
2009-10-26 14:46 ` LC Bruzenak
2009-10-30 14:56 ` Steve Grubb
2009-11-14 1:14 ` LC Bruzenak
2009-11-16 15:59 ` Steve Grubb
2009-11-16 23:52 ` LC Bruzenak
2009-11-17 21:48 ` Steve Grubb
2009-11-18 3:52 ` LC Bruzenak
2009-11-18 4:16 ` LC Bruzenak [this message]
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=cecd18b00911172016n46ae1014wf1de81c395e5f6cd@mail.gmail.com \
--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