On Thu, Jul 03, 2003 at 11:10:45AM +0300, Muli Ben-Yehuda wrote:
> On Thu, Jul 03, 2003 at 10:56:29AM +0300, [EMAIL PROTECTED] wrote:
> > What was that syscalltrace?
>
> http://syscalltrack.sf.net
Thanks. Sounds like just what I was after, including a Debian package.
>
> > I'm looking for tools in that area and couldn't find such a program
> > in google or otherwise (specifically - I'm thinking of something which
> > will report to me all the paths passed to execve(2) anywere in the
> > system, the closest I found so far is the LinuxTraceToolkit (LTT) but
> > I suspect it's too heavy for my needs).
>
> Why is ltt too heavy?
Because all I want is to have a list of file names (and maybe times),
LTT gives much much more about many more things and looks farheavier to
setup and run.
For instance, from reading the docs of syscalltrack all I'll have
to do is to configure it with:
rule {
syscall_name = execle
when = before
action { type = LOG }
}
And get exactly what I want (hmmm, lots of shell/perl hacking on the output,
yummi yummi....:)
Thanks,
--Amos
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
