From: Paul Moore <paul@paul-moore.com>
To: burn@swtf.dyndns.org
Cc: Richard Guy Briggs <rgb@redhat.com>,
Linux Audit <linux-audit@redhat.com>
Subject: Re: Occasional delayed output of events
Date: Wed, 20 Jan 2021 17:50:23 -0500 [thread overview]
Message-ID: <CAHC9VhT9N6Ztpt3pwE0CMaHyKrwoOWLZuB3vTnq_mpxnkgvfPQ@mail.gmail.com> (raw)
In-Reply-To: <ebcdc0bc829e126c9fb9747b2457c5211527c8b1.camel@iinet.net.au>
On Wed, Jan 20, 2021 at 1:38 AM Burn Alting <burn.alting@iinet.net.au> wrote:
> All,
>
> How is the following for a way forward.
>
> a. I will author a patch to the user space code to correctly parse this condition and submit it on the weekend. It will be via a new configuration item to auditd.conf just in case placing a fixed extended timeout (15-20 secs) affects memory usage for users of the auparse library. This solves the initial problem of ausearch/auparse failing to parse generated audit.
> b. I am happy to instrument what ever is recommended on my hosts at home (vm's and bare metal) to provide more information, should we want to 'explain' the occurrence, given I see this every week or two and report back.
Seems reasonable to me.
--
paul moore
www.paul-moore.com
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2021-01-20 22:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 21:22 Occasional delayed output of events Burn Alting
2021-01-03 15:41 ` Steve Grubb
2021-01-04 7:55 ` Burn Alting
2021-01-04 14:46 ` Steve Grubb
2021-01-04 20:12 ` Burn Alting
2021-01-10 4:39 ` Burn Alting
2021-01-15 22:18 ` Burn Alting
2021-01-16 0:35 ` Richard Guy Briggs
2021-01-16 2:42 ` Burn Alting
2021-01-17 14:07 ` Paul Moore
2021-01-17 21:12 ` Steve Grubb
2021-01-18 13:54 ` Paul Moore
2021-01-18 14:31 ` Steve Grubb
2021-01-18 20:34 ` Burn Alting
2021-01-18 20:36 ` Paul Moore
2021-01-19 8:18 ` Burn Alting
2021-01-19 15:31 ` Lenny Bruzenak
2021-01-19 19:11 ` Paul Moore
2021-01-19 19:38 ` Burn Alting
2021-01-19 20:26 ` Paul Moore
2021-01-19 21:51 ` Steve Grubb
2021-01-20 6:38 ` Burn Alting
2021-01-20 22:50 ` Paul Moore [this message]
2021-01-23 22:55 ` Burn Alting
2021-01-25 23:53 ` Steve Grubb
2021-01-26 0:11 ` Burn Alting
2021-01-26 0:20 ` Steve Grubb
2021-01-26 0:29 ` Burn Alting
2021-01-26 11:53 ` Burn Alting
2021-01-26 20:42 ` Steve Grubb
2021-01-27 12:12 ` Burn Alting
2021-01-19 20:42 ` Richard Guy Briggs
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=CAHC9VhT9N6Ztpt3pwE0CMaHyKrwoOWLZuB3vTnq_mpxnkgvfPQ@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=burn@swtf.dyndns.org \
--cc=linux-audit@redhat.com \
--cc=rgb@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.