NFSLOGSUM(8)

💖 NAME 💖

ok so nfslogsum — she summarizes nfswatch log files. that's the whole job bestie, and she does it flawlessly ✨

---

🎀 SYNOPSIS 🎀

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

---

🌸 DESCRIPTION 🌸

okay so here's the tea: nfslogsum takes the log files that nfswatch produces and turns them into an actual summary, because reading raw logs is not the vibe. 🫶

by default she summarizes the log file nfswatch.log. want a different one? just drop an alternate log file on the command line, easy. 💅

every nfswatch log file can hold one or more log sessions, and each one starts with a header that gets printed whenever logging is turned on. for each session, nfslogsum tallies up the interval packet totals and prints a one-page summary of that session. total packets and percentages? tabulated for each category, and displayed. periodt. 📊

the -n option tells nfslogsum to read only the first n entries in the log file. this is lowkey iconic for summarizing log files in cumulative "chunks". 🧩

if the -v option is given, nfslogsum produces a "verbose" summary of the log file. on top of everything described above, you also get a summary of how many calls to each NFS procedure were made on each file system and on each individual file. this summary is split into three sections of six columns each, and the columns are headed by the names of the NFS procedures. here's the rundown, briefly: 👑

• NULLPROC — do nothing. this procedure exists so you can do server response testing and timing.
• GETATTR — get file attributes (type, mode, number of links, owner's uid, owner's gid, size, access, modification and change times, etc.). used by the stat(2) system call, plus several others.
• SETATTR — set file attributes (mode, owner's uid, owner's gid, size in bytes, access and modification times). used by system calls like chmod(2), chown(2), truncate(2), and so on.
• GETROOT — get file system root. this procedure is obsolete, and has been replaced by a MOUNT Protocol procedure. 💀
• LOOKUP — look up file name. used to obtain an initial file handle for use in current and future requests on that file, and it's used by many different system calls.
• READLINK — read from symbolic link. used by the readlink system call, and by the kernel.
• READ — read data from file. used by the read(2) system call.
• WCACHE — write to cache. unused in the current NFS protocol revision. 🙈
• WRITE — write data to file. used by the write(2) system call.
• CREATE — create file. used by the creat(2) and open(2) system calls.
• REMOVE — remove file. used by the unlink(2) system call.
• RENAME — rename file. used by the rename system call.
• LINK — create link to file. used by the link(2) system call.
• SYMLINK — create symbolic link to file. used by the symlink(2) system call.
• MKDIR — create directory. used by the mkdir(2) system call.
• RMDIR — remove directory. used by the rmdir(2) system call.
• READDIR — read entries from directory. generally only one READDIR call is needed per directory, since a variable number of entries can be returned. efficiency queen 🌈
• STATFS — get file system attributes (transfer size, block size, blocks in use, blocks free). used by the statfs(2) system call.

---

🦋 SEE ALSO 🦋

• nfswatch(8)

---

💀 BUGS 💀

nfslogsum is extremely sensitive to the format of the log file produced by nfswatch. do not edit or change the log file before feeding it to nfslogsum. not even a little. not even one character. she will notice and she will act up. 😭

---

✨ AUTHOR ✨

David A. Curry Purdue University Engineering Computer Network 1285 Electrical Engineering Building West Lafayette, IN 47907-1285 davy@ecn.purdue.edu

---

and that's the whole page bestie 💜 this one came out of the Purdue/DEC System Manager's Manual, dated January 1993 — vintage, but the girlies still use her. bye now, go summarize some logs 🎀