From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: How to track process invocation history using audit Date: Mon, 20 Jun 2011 12:04:00 -0400 Message-ID: <201106201204.01044.sgrubb@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com List-Id: linux-audit@redhat.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