What do you want to find out that you couldn't get by tracking *make and its descendant processes, down to whatever level you desire? Are there parts of *make's "reasoning" you'd like to understand or is this just a matter of convenience?
Perhaps with a use case or two to consider, folks may be able to make appropriate suggestions. -r -- http://www.cfcl.com/rdm Rich Morin http://www.cfcl.com/rdm/resume [EMAIL PROTECTED] http://www.cfcl.com/rdm/weblog +1 650-873-7841 Technical editing and writing, programming, and web development _______________________________________________ dtrace-discuss mailing list [email protected]
