On Mon, 17 Apr 2006, Spencer Shepler wrote: > > So the best way I can think of to accomplish what you want is to > hook each of the VOP entry points in the NFSv3 client code (which have > likely done already) and then track use of rfs3call. As you note, > this will capture all over-the-wire activity for the NFSv3 client > VOP in question. In fact, you will be able to capture if the client > does more than one RPC to satisfy the upper level VOP call.
Cool. I will conduct some tests this week. > As you note, this works for everything except asynchronous events the > client does. This would be things like read, write, and async readdir. > For those, I would suggest tracking use of nfs3read, nfs3write and checking > the vnode in question (by matching with the initial vnode used for the VOP > call); nfs3read/nfs3write will do over-the-wire work so that is an > easy match. Which field(s) in the vnode_t would you recommend matching against? Do you by any chance have a sample D script that could illustrate this? > For readdir, you will want to track the nfs3readdir and nfs3readdirplus > with the vnode tracking and that should track that behavior as well. Thanks. I will add these routines to the list of stuff to study. Thanks for the feedback, - Ryan -- UNIX Administrator http://daemons.net/~matty
