From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Help with audit syscall event output
Date: Tue, 03 Sep 2019 17:24:39 -0400 [thread overview]
Message-ID: <12155994.AWt580abvh@x2> (raw)
In-Reply-To: <CAG-5c_G5ULcbh_TEZEefm0VM8XeDW=OJoLBVRq+1=VO-BtMczA@mail.gmail.com>
On Tuesday, September 3, 2019 5:15:29 PM EDT Ankitha Kundhuru wrote:
> Any help is greatly appreciated.
>
> My piece of code can read audit.log file and process it.But when I enable
> good number of syscalls, disk gets filled really quick (15GB for half a day
> usage)
> I wanted to know if there is a way to directly get the events from
> userspace audit daemon instead of writing it to a file. Plan is that my
> application should process the events as soon as they are created.
Yes, there is a presentation that describes the architecture of the audit
system including the realtime event interface:
http://people.redhat.com/sgrubb/audit/audit_ids_2011.pdf
And there is sample code for a plugin here:
https://github.com/linux-audit/audit-userspace/tree/master/contrib/plugin
-Steve
next prev parent reply other threads:[~2019-09-03 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 21:15 Help with audit syscall event output Ankitha Kundhuru
2019-09-03 21:24 ` Steve Grubb [this message]
2019-09-03 21:28 ` Ankitha Kundhuru
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=12155994.AWt580abvh@x2 \
--to=sgrubb@redhat.com \
--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 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.