From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: How to track process invocation history using audit
Date: Mon, 20 Jun 2011 12:04:00 -0400 [thread overview]
Message-ID: <201106201204.01044.sgrubb@redhat.com> (raw)
In-Reply-To: <BANLkTikdGQZe_kYaRJs=PQZk9dTYnbFdMg@mail.gmail.com>
On Monday, June 20, 2011 11:51:10 AM Kohei KaiGai wrote:
> I tried to track all the fork(2) system call to record relationship
> between ppid and pid
> on processes with a particular loginuid.
>
> [root@ls3029v0 ~]# auditctl -a task,always -F arch=b64 -S fork -F
> auid=1234 Error: syscall auditing being added to task list
Maybe you need to use the clone syscall? You can probably strace a program just to
make sure what its using.
-Steve
prev parent reply other threads:[~2011-06-20 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 15:51 How to track process invocation history using audit Kohei KaiGai
2011-06-20 16:04 ` Steve Grubb [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=201106201204.01044.sgrubb@redhat.com \
--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.