Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

nfslogsum(8) [osf1 man page]

nfslogsum(8)						      System Manager's Manual						      nfslogsum(8)

NAME
nfslogsum - Summarize nfswatch log file SYNOPSIS
/usr/sbin/nfslogsum [-n] [-v] [logfile] OPTIONS
Directs nfslogsum to read only the first n entries in the log file. This is useful for summarizing log files in cumulative chunks. Pro- duces a verbose summary of the log file. DESCRIPTION
The nfslogsum command summarizes log files produced by the nfswatch program. By default the log file nfswatch.log is summarized; an alter- nate 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. In addition to the summary information printed as described above, a summary of how many calls to each NFS 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 following NFS procedures: Does nothing. This procedure is provided to allow server response testing and timing. Gets the file attributes (type, mode, number of links, owner's uid, owner's gid, size, access, modification and change times, and others). This procedure is used by the stat(2) system call, as well as several others. Sets the 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), and truncate(2). Gets the file system root. This procedure is obsolete, and has been replaced by a MOUNT protocol procedure. Looks up the file name. This proce- dure 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. Reads from the symbolic link. This procedure is used by the readlink system call and by the kernel. Reads data from the file. This procedure is used by the read(2) system call. Writes to the cache. Unused in the current NFS protocol revision. Writes data to a file. This procedure is used by the write(2) system call. Creates a file. This procedure is used by the creat(2) and open(2) system calls. Removes a file. This procedure is used by the unlink(2) system call. Renames a file. This procedure is used by the rename system call. Creates a link to the file. This procedure is used by the link(2) system call. Creates a symbolic link to the file. This procedure is used by the symlink(2) system call. Creates a directory. This procedure is used by the mkdir(2) system call. Removes a directory. This proce- dure is used by the rmdir(2) system call. Reads entries from a directory. Generally only one READDIR call is needed per directory, since a variable number of entries can be returned. Gets file system attributes (transfer size, block size, blocks in use, blocks free). This pro- cedure is used by the statfs(2) system call. RESTRICTIONS
The nfslogsum utility is sensitive to the format of the log file produced by nfswatch. Do not edit or change the log file before using it as input to nfslogsum. SEE ALSO
Commands: nfswatch(8), tcpdump(8) Networking: bpf(7), packetfilter(7) nfslogsum(8)

Check Out this Related Man Page

log(8)							      System Manager's Manual							    log(8)

NAME
log - Records input and output from a program SYNOPSIS
/usr/sbin/log <logfile> <command> OPERANDS
The file in which to record the interaction being logged. The command to execute. DESCRIPTION
The log program runs <command> and logs the input to and output from <command> to the <logfile> file. Input and output are logged until <command> exits, the log program exits, and the exit status of <command> is returned. The log program is used by the system installation procedure and the it(8) command to create the /var/adm/smlogs/install.log and /var/adm/smlogs/it.log installation log files. RESTRICTIONS
Because the log program is used in the installation standalone environment, program size was the greatest concern in its implementation. The log program does not search for the PATH variable to locate <command> and error messages are terse. The log program causes <command> to take standard input from and write standard output and standard error to UNIX pipes. Some commands will not be able to operate in this environment; therefore, it is suggested that you use the script(1) command instead. UNIX shells will not issue prompts when run from log unless the shell is started with an explicit interactive switch (-i for most shells). For example, log foo.tmp /sbin/sh -i In the previous example, foo.tmp is the name of <logfile>. The log program intercepts end-of-file (usually Ctrl/d). Therefore programs which normally receive end-of-file as an exit command must exit by some other means. ERRORS
Log open error Explanation: The log program was unable to open <logfile>. Verify that the directory exists and that ownerships and permissions are set correctly. Exec Error Explanation: The log program was unable to execute <command>. Verify that you specified a full pathname for <command> and that <command> is an exe- cutable file. Fork Error Explanation: The log program was unable to create one of the processes it requires to log data. SEE ALSO
Commands: it(8), script(1) log(8)
Man Page