lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8249.1329194664@turing-police.cc.vt.edu>
Date:	Mon, 13 Feb 2012 23:44:24 -0500
From:	Valdis.Kletnieks@...edu
To:	Michael Opdenacker <michael.opdenacker@...e-electrons.com>
Cc:	ranjith kumar <ranjithproxy@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: how to know list of files accessed

On Mon, 13 Feb 2012 13:32:56 +0100, Michael Opdenacker said:

> An easy way is to run your command with 'strace' to trap all the calls
> to 'open':
>
> strace make 2>&1 | grep open

You really want 'strace -f make' - the -f flag makes it follow forks, which you
want to do because it's gcc that's doing most of the actual file I/O, not make.

Oh.  and you want to redirect that grep into a temporary file and be
prepared to post-process it with perl or something, there's going to be
*zillions* of open() syscalls.

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ