* Help with audit syscall event output
@ 2019-09-03 21:15 Ankitha Kundhuru
2019-09-03 21:24 ` Steve Grubb
0 siblings, 1 reply; 3+ messages in thread
From: Ankitha Kundhuru @ 2019-09-03 21:15 UTC (permalink / raw)
To: linux-audit
[-- Attachment #1.1: Type: text/plain, Size: 489 bytes --]
Hi All,
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.
Suggest me if a way exist.
Thanks in advance.
Thanks & Regards,
Ankitha Kundhuru
[-- Attachment #1.2: Type: text/html, Size: 753 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Help with audit syscall event output
2019-09-03 21:15 Help with audit syscall event output Ankitha Kundhuru
@ 2019-09-03 21:24 ` Steve Grubb
2019-09-03 21:28 ` Ankitha Kundhuru
0 siblings, 1 reply; 3+ messages in thread
From: Steve Grubb @ 2019-09-03 21:24 UTC (permalink / raw)
To: linux-audit
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Help with audit syscall event output
2019-09-03 21:24 ` Steve Grubb
@ 2019-09-03 21:28 ` Ankitha Kundhuru
0 siblings, 0 replies; 3+ messages in thread
From: Ankitha Kundhuru @ 2019-09-03 21:28 UTC (permalink / raw)
To: Steve Grubb; +Cc: linux-audit
[-- Attachment #1.1: Type: text/plain, Size: 958 bytes --]
Awesome, thanks!
Thanks & Regards,
Ankitha Kundhuru
On Tue, Sep 3, 2019 at 5:24 PM Steve Grubb <sgrubb@redhat.com> wrote:
> 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
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 1709 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-09-03 21:28 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-09-03 21:15 Help with audit syscall event output Ankitha Kundhuru
2019-09-03 21:24 ` Steve Grubb
2019-09-03 21:28 ` Ankitha Kundhuru
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox