Hi, i am not an expert kernel programmer. But I think device drivers should help you solve the problem. But you will have to figure out a mechanism for storing the state from the kernel(i mean the exact control sequence). If it is the networking stack then netfilter is the option - otherwise a naive approach is to change the kernel code and recompile the kernel. But this is not preffered. May be if you tell te exact nature of the information to be stored then someone can suggest that mechanism. The position at which you will re-introduce the information back into the kernel is also problem specific. So I guess we need to know more about the information being handled. -Pradeep ____________________________ I'm trying ti develop a file monitor mechanism, I mean: when a sys_open | sys_exec system call arise I'd like to do something with that file in a user space app (daemon). The problem is that I need my module "waits??" until the user land daemon finish with the file processing. I was given the following answer: Instead of thinking about the kernel module > waiting think about the kernel module remembering enough state on a > queue But sincerely I don't know what that means about. thanks in advance isr@el -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ IRC Channel: irc.openprojects.net / #kernelnewbies Web Page: http://www.kernelnewbies.org/