hello, neil,
in fixing the has_stats()'s-false-positives bug, i've come across
some existing assumptions in the code about the number of elements in a
given stat type -- e.g., the number of NFSv4 client "operations" being
tallied.
in that specific case, three new counts in /proc/net/rpc/nfs have
been added that nfsstat doesn't currently acknowledge: GETACL, SETACL, and
FS_LOCATIONS, i believe.
the manner in which i fix the has_stats() bug depends on how
closely nfsstat is intended to stay synchronized with the data in
/proc/net/rpc/nfs. since these aren't actual NFSv4 procedures, i'm not
quite sure what folks expect.
please let me know what you think.
thanks,
d
.
_____
david m. richter
CITI -- Center for Information Technology Integration
http://www.citi.umich.edu
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs