1CMON(1) CMON(1)
2
6 cmon - Coda server monitor
7
9 cmon [ -a ] [ -t probeinterval ] server [ server ... ]
10
13 cmon probes the specified list of servers once every probeinterval sec‐
14 onds and reports on their status. If a server is down or unreachable,
15 cmon tries to reestablish contact with it once every probeinterval sec‐
16 onds. It uses the curses(3) package for screen management and can be
17 used on dumb terminals. Run cmon in a terminal emulator (like
18 xterm(1)).
19 Some cmon data can be displayed in relative or absolute modes. In rel‐
21 ative mode, data is reported with reference to the interval between the
22 last two probes. In absolute mode, the accumulated value since ini‐
23 tialization is reported. cmon can be toggled between absolute and real
24 modes of presentation from the keyboard. Typing a will cause data to
25 be presented in absolute mode. Typing r will present it in relative
26 mode. A mode change will only take place at the next probe.
27
29 The command-line options are:
30 -a Report data in absolute mode.
32 -t Probe servers every probeinterval seconds. Default is 60.
34
36 The data reported by cmon is organized under four headings: TIM, CPU,
37 RPC, and DSK.
38 The TIM data is as follows:
40 mon time at which this cmon process was created.
42 prob time at which the server was last probed.
44 succ time at which the server last responded to a probe.
46 up time at which the server process was started.
48 bind number of times contact was reestablished after a failed probe.
50 A probe may fail due to server or network failures.
51 The CPU data is as follows:
53 sys Relative or absolute number of seconds of system CPU time used
55 on the server.
56 user Relative or absolute number of seconds of user CPU time (regular
58 or niced) used on the server.
59 util Relative or absolute number of system and user seconds divided
61 by corresponding time of accumulation.
62 The RPC data is as follows:
64 conn Number of RPC connections.
66 wkst Number of workstations connected to server. Note that each
68 instance of cmon shows up as a workstation.
69 call Relative or absolute number of RPC calls received.
71 pki Relative or absolute number of RPC packets received. Includes
73 duplicates and other bogus packets. Also includes bulk transfer
74 packets.
75 pko Relative or absolute number of packets sent. Includes retrans‐
77 missions. Also includes bulk transfer packets.
78 byi Bytes corresponding to pki.
80 byo bytes corresponding to pko.
82 The DSK data is as follows:
84 max1 Identity and percent usage of most full disk partition on
86 server. The identity is the name of mount point. Names longer
87 than 5 characters are truncated to the first 3 characters, a $
88 character, and the last character.
89 max2 Identity and percent usage of second most full disk.
91 max3 Identity and percent usage of third most full disk.
93
95 If a server is down or unreachable, statisitics for it are reported as
96 "???".
97 Relative data is undefined until two or more probes have been made.
99 Such data is reported as "***" between the very first and second
100 probes.
101
103 · Relative computations are just based on the difference between the
104 two most recent probes. A smarter approach (especially for CPU uti‐
105 lization) would be to use some kind of weighted history.
106 · The display is optimized for maximum packing of information into a
108 small screen area. It may be cryptic for a novice.
109 · No disk information is available about the root partition on a
111 server.
112 · Will core dump if run in a window with fewer than 25 lines.
114 · No way to force a redisplay (eg ^L).
116
118 codacon(1), vutil(8), curses(3)
119
121 · M. Satyanarayanan, 1990, Created
122Coda Distributed File System 25 April 2005 CMON(1)