Quoting Chris Wright <chrisat_private> on Thu, Jul 24 10:56: > > The short answer is, you can't. There is nothing that guarantees a > single canonical path to an inode. Think hard links, multiple mount > points, and bind mounts. Hmmm, maybe I'm approaching all of this from the wrong hook then. Maybe file_permission is what I want. So, new questions. If file_permission gets called for every read/write call, is there an easy way to detect the very first call? If I tap file_permission will that cover all ways for a file/program/library to get loaded or executed? I guess the hook I really want is a file_open hook, but that seems to be inode_permission, which does not seem to be the hook I want. Ack, I'm confused. -- It's 3:15 -- do you know where your child processes are?
This archive was generated by hypermail 2b30 : Thu Jul 24 2003 - 12:52:54 PDT