On Friday 23 February 2007 02:11, Amos Shapira wrote: > Assuming the above (i.e. files are mostly not written concurrently by > multiple processes), maybe you can try to track write(2) system calls. > Mulli's old syscalltack (http://syscalltrack.sourceforge.net/) should have > been able to do this for you if it was still relevant for current kernels > (is it?)
I wonder if it is still relevant? Can someone say what are the advantages of using (=after porting of course) syscalltrack in 2.6 kernel over existing solutions. Like, for example, debugging uml, using kprobes, etc... In addition, i think that in 2.4 there was some kind of syscall table which was exported and which you could replace syscall functions, but in 2.6 they stopped this practice and made this technique obsolete if not highly difficult/impossible. > > --Amos -- Regards, Tzahi. -- Tzahi Fadida Blog: http://tzahi.blogsite.org | Home Site: http://tzahi.webhop.info WARNING TO SPAMMERS: see at http://members.lycos.co.uk/my2nis/spamwarning.html ================================================================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]
