From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: SIGXCPU and Auditd
Date: Tue, 05 Nov 2013 08:27:28 -0500 [thread overview]
Message-ID: <7362085.zRoRGRkC6K@x2> (raw)
In-Reply-To: <5278EDF0.3050804@gmail.com>
On Tuesday, November 05, 2013 06:39:04 PM Paul Davies C wrote:
> Hi,
>
> Is there any way to make the *auditd system to log the SIGXCPU signal*?
> As of now , without writing any specific rules, SIGSEGV is getting
> logged. In my log I found lines as below :
> /
> type=ANOM_ABEND msg=audit(1383644379.989:88): auid=1000 uid=1000
> gid=1000 ses=5 pid=2688 comm="chrome" reason="memory violation" sig=11/
The ABnormal END event is triggered by any event that would be terminated by
the kernel with a core dump. Looking at the signal(7) man page, SIGXCPU by
default would core. So, it should trigger an event. I don't have a test case
to prove it, though.
Steve
next prev parent reply other threads:[~2013-11-05 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 13:09 SIGXCPU and Auditd Paul Davies C
2013-11-05 13:27 ` Steve Grubb [this message]
2013-11-05 13:46 ` Paul Davies C
2013-11-05 14:02 ` Steve Grubb
2013-11-11 10:54 ` Paul Davies C
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=7362085.zRoRGRkC6K@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox