how to know the parameters of sys_open and sys_unlink system calls of all apps.
rakesh_usenet_at_yahoo.com
Date: 01/11/05
- Next message: Timo Stöckigt: "Re: Opening a door with a cell phone"
- Previous message: Josef Moellers: "Re: Opening a door with a cell phone"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 11 Jan 2005 01:53:26 -0800
Hi,
I am writing this application that is designed as follows.
* the app. would run in the bg . As long as the app is running on the
system, all the files created and deleted by different applications
ought to be tracked by this daemon. So essentially it reduces to
getting the parameters of sys_open and sys_unlink system calls.
I was looking at different ways of implementing it.
* strace : This one was appealing to me but actually this is not
transparent , in the sense, that we explicitly invoke this to get the
system call parameters and return values.
I was wondering as to how to implement them. I am going through
Alessandro rubbini's linux device drivers' book with the first couple
of chapters about writing a module of our own.
My idea is that I want to write a module such that - when the module
is loaded - it would keep track of all the files that were created and
deleted. And the module would work on the data separately. I am pretty
much very new to Linux kernel programming so please let me know some
design pointers as to how I accomplish this
- Next message: Timo Stöckigt: "Re: Opening a door with a cell phone"
- Previous message: Josef Moellers: "Re: Opening a door with a cell phone"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|