SYNOPSIS

nfslogsum [ -n ] [ -v ] [ logfile ]

DESCRIPTION

nfslogsum summarizes log files produced by the nfswatch program. By default the log file nfswatch.log is summarized; an alternate log file can be specified on the command line.

Each nfswatch log file may contain one or more log sessions, each indicated by a header which is printed when logging is turned on. For each log session, nfslogsum tallies up the interval packet totals and prints out a one-page summary of the log session. Total packets and percentages are tabulated for each category and displayed.

The -n option tells nfslogsum to read only the first n entries in the log file. This is useful for summarizing log files in cumulative ``chunks''.

If the -v option is given, nfslogsum will produce a ``verbose'' summary of the log file. In addition to the summary information printed as described above, a summary of how many calls to each \*(@N procedure were made on each file system and individual file will be printed. This summary information is divided into three sections of six columns each. The columns are headed by the names of the \*(@N procedures; these are described briefly below:

\s-1NULLPROC\s0

Do nothing. This procedure is provided to allow server response testing and timing.

\s-1GETATTR\s0

Get file attributes (type, mode, number of links, owner's uid, owner's gid, size, access, modification and change times, etc.). This procedure is used by the stat(2) system call, as well as several others.

\s-1SETATTR\s0

Set file attributes (mode, owner's uid, owner's gid, size in bytes, access and modification times). This procedure is used by system calls such as chmod(2), chown(2), truncate(2), and so on.

\s-1GETROOT\s0

Get file system root. This procedure is obsolete, and has been replaced by a \s-1MOUNT\s0 Protocol procedure.

\s-1LOOKUP\s0

Look up file name. This procedure is used to obtain an initial file handle for use in current and future requests on that file, and is used by many different system calls.

\s-1READLINK\s0

Read from symbolic link. This procedure is used by the readlink system call, and by the kernel.

\s-1READ\s0

Read data from file. This procedure is used by the read(2) system call.

\s-1WCACHE\s0

Write to cache. Unused in the current \*(@N protocol revision.

\s-1WRITE\s0

Write data to file. This procedure is used by the write(2) system call.

\s-1CREATE\s0

Create file. This procedure is used by the creat(2) and open(2) system calls.

\s-1REMOVE\s0

Remove file. This procedure is used by the unlink(2) system call.

\s-1RENAME\s0

Rename file. This procedure is used by the rename system call.

\s-1LINK\s0

Create link to file. This procedure is used by the link(2) system call.

\s-1SYMLINK\s0

Create symbolic link to file. This procedure is used by the symlink(2) system call.

\s-1MKDIR\s0

Create directory. This procedure is used by the mkdir(2) system call.

\s-1RMDIR\s0

Remove directory. This procedure is used by the rmdir(2) system call.

\s-1READDIR\s0

Read entries from directory. Generally only one \s-1READDIR\s0 call is needed per directory, since a variable number of entries can be returned.

\s-1STATFS\s0

Get file system attributes (transfer size, block size, blocks in use, blocks free). This procedure is used by the statfs(2) system call.

RELATED TO nfslogsum…

BUGS

nfslogsum is exteremely sensitive to the format of the log file produced by nfswatch. The log file should not be edited or changed before feeding it to nfslogsum.

AUTHOR

David A. Curry

Purdue University

Engineering Computer Network

1285 Electrical Engineering Building

West Lafayette, \s-1IN\s0 47907-1285

[email protected]