1NFSLOGSUM(8L) NFSLOGSUM(8L)
2
3
4
6 nfslogsum - summarize nfswatch log file
7
9 nfslogsum [ -n ] [ -v ] [ logfile ]
10
12 nfslogsum summarizes log files produced by the nfswatch program. By
13 default the log file nfswatch.log is summarized; an alternate log file
14 can be specified on the command line.
15
16 Each nfswatch log file may contain one or more log sessions, each indi‐
17 cated by a header which is printed when logging is turned on. For each
18 log session, nfslogsum tallies up the interval packet totals and prints
19 out a one-page summary of the log session. Total packets and percent‐
20 ages are tabulated for each category and displayed.
21
22 The -n option tells nfslogsum to read only the first n entries in the
23 log file. This is useful for summarizing log files in cumulative
24 ``chunks''.
25
26 If the -v option is given, nfslogsum will produce a ``verbose'' summary
27 of the log file. In addition to the summary information printed as
28 described above, a summary of how many calls to each NFS procedure were
29 made on each file system and individual file will be printed. This
30 summary information is divided into three sections of six columns each.
31 The columns are headed by the names of the NFS procedures; these are
32 described briefly below:
33
34 NULLPROC
35 Do nothing. This procedure is provided to allow server response
36 testing and timing.
37
38 GETATTR
39 Get file attributes (type, mode, number of links, owner's uid,
40 owner's gid, size, access, modification and change times, etc.).
41 This procedure is used by the stat(2) system call, as well as
42 several others.
43
44 SETATTR
45 Set file attributes (mode, owner's uid, owner's gid, size in
46 bytes, access and modification times). This procedure is used
47 by system calls such as chmod(2), chown(2), truncate(2), and so
48 on.
49
50 GETROOT
51 Get file system root. This procedure is obsolete, and has been
52 replaced by a MOUNT Protocol procedure.
53
54 LOOKUP Look up file name. This procedure is used to obtain an initial
55 file handle for use in current and future requests on that file,
56 and is used by many different system calls.
57
58 READLINK
59 Read from symbolic link. This procedure is used by the readlink
60 system call, and by the kernel.
61
62 READ Read data from file. This procedure is used by the read(2) sys‐
63 tem call.
64
65 WCACHE Write to cache. Unused in the current NFS protocol revision.
66
67 WRITE Write data to file. This procedure is used by the write(2) sys‐
68 tem call.
69
70 CREATE Create file. This procedure is used by the creat(2) and open(2)
71 system calls.
72
73 REMOVE Remove file. This procedure is used by the unlink(2) system
74 call.
75
76 RENAME Rename file. This procedure is used by the rename system call.
77
78 LINK Create link to file. This procedure is used by the link(2) sys‐
79 tem call.
80
81 SYMLINK
82 Create symbolic link to file. This procedure is used by the
83 symlink(2) system call.
84
85 MKDIR Create directory. This procedure is used by the mkdir(2) system
86 call.
87
88 RMDIR Remove directory. This procedure is used by the rmdir(2) system
89 call.
90
91 READDIR
92 Read entries from directory. Generally only one READDIR call is
93 needed per directory, since a variable number of entries can be
94 returned.
95
96 STATFS Get file system attributes (transfer size, block size, blocks in
97 use, blocks free). This procedure is used by the statfs(2) sys‐
98 tem call.
99
101 nfswatch(8L)
102
104 nfslogsum is exteremely sensitive to the format of the log file pro‐
105 duced by nfswatch. The log file should not be edited or changed before
106 feeding it to nfslogsum.
107
109 David A. Curry
110 Purdue University
111 Engineering Computer Network
112 1285 Electrical Engineering Building
113 West Lafayette, IN 47907-1285
114 davy@ecn.purdue.edu
115
116
117
118Purdue/DEC January 1993 NFSLOGSUM(8L)