table of contents
XOSVIEW(1) | General Commands Manual | XOSVIEW(1) |
NAME¶
xosview - X based system monitorSYNOPSIS¶
xosview [options]DESCRIPTION¶
xosview is a monitor which displays the status of several system based parameters. These include CPU usage, load average, memory, swap space, network usage and more. Each resource is displayed as a horizontal bar which is separated into color coded regions showing how much of the resource which is being put to a particular use.Linux : user | nice | system | soft-interrupt | interrupt | io-wait | guest | stolen | idle
*BSD : user | nice | system | interrupt | idle
IRIX : user | system | interrupt | wait | idle
HPUX : user | nice | system | interrupt | idle
Linux : used | buffers | slab | map | cache | free
NetBSD : active | inactive | wired | free
FreeBSD: active | inactive | wired | buffer | free
OpenBSD: active | inactive | wired | free
IRIX : kernel | fs | user | free
HPUX : text | used | other | free
GNU : active | inactive | wired | free
Linux : used | free
*BSD : used | free
HPUX : used | free
GNU : used | free
Linux : in | out | idle
*BSD : transferred | idle
Linux : in | out | idle
*BSD : in | out | idle
HPUX : in | out | idle
GNU : in | out | idle
Linux : in | out | idle
*BSD : in | out | idle
IRIX : swapbuffers
Linux : IRQs
*BSD : IRQs
*BSD : interrupts | free
Linux : LSR and MSR
Linux : available | used
NetBSD : available | used
OpenBSD: available | used
Linux : disk0 disk1 disk2 ... diskN | rebuild
Linux : quality
OPTIONS¶
Most of these command line options are just a convenient way to set one or more of xosview's resources. Please see the RESOURCES section for more details on what the resource is for.Displays the version number.
Sets the Resource name xosview will use (same
as the -name option for typical X applications like xterm). When performing
resource lookups, xosview will look under name, and then under
``xosview''. For an example, perform the following (as documented in
README.netbsd):
xrdb -merge Xdefaults.stipple
xosview -name xosvstipple &
xosview -name xosvstipplebw &
xrdb -merge Xdefaults.stipple
xosview -name xosvstipple &
xosview -name xosvstipplebw &
Sets the X display to display. This
option overrides the xosview*display resource.
Specifies the font xosview will use for
labels. This option overrides the xosview*font resource.
This option sets the name xosview will tell
the window manager to use for the X window and icon. This option overrides the
xosview*title resource.
Sets the X geometry to geometry_string.
This option overrides the xosview*geometry resource.
This option overrides the xosview*captions
resource. It is equivalent to setting xosview*captions to
"False".
+captions
This option overrides the xosview*captions
resource. It is equivalent to setting xosview*captions to
"True".
This option overrides the xosview*labels
resource. It is equivalent to setting xosview*labels to
"False".
+labels
This option overrides the xosview*labels
resource. It is equivalent to setting xosview*labels to
"True".
This option overrides the xosview*usedlabels
resource. It is equivalent to setting xosview*usedlabels to
"False".
This option overrides the xosview*usedlabels
resource. It is equivalent to setting xosview*usedlabels to
"True".
This option overrides the xosview*cpu
resource. It is equivalent to setting xosview*cpu to "False".
+cpu
This option overrides the xosview*cpu
resource. It is equivalent to setting xosview*cpu to "True".
This option overrides the xosview*load
resource. It is equivalent to setting xosview*load to "False".
+load
This option overrides the xosview*load
resource. It is equivalent to setting xosview*load to "True".
This option overrides the xosview*mem
resource. It is equivalent to setting xosview*mem to "False".
+mem
This option overrides the xosview*mem
resource. It is equivalent to setting xosview*mem to "True".
This option overrides the xosview*swap
resource. It is equivalent to setting xosview*swap to "False".
+swap
This option overrides the xosview*swap
resource. It is equivalent to setting xosview*swap to "True".
This option overrides the xosview*battery
resource. It is equivalent to setting xosview*battery to
"False".
+battery
This option overrides the xosview*battery
resource. It is equivalent to setting xosview*battery to
"True".
This option overrides the xosview*gfx
resource. It is equivalent to setting xosview*gfx to "False".
+gfx
This option overrides the xosview*gfx
resource. It is equivalent to setting xosview*gfx to "True".
This option overrides the xosview*wireless
resource. It is equivalent to setting xosview*wireless to
"False".
+wireless
This option overrides the xosview*wireless
resource. It is equivalent to setting xosview*wireless to
"True".
This option overrides the xosview*net
resource. It is equivalent to setting xosview*net to "False".
+net
This option overrides the xosview*net
resource. It is equivalent to setting xosview*net to "True".
These options override the
xosview*netBandwidth resource. They cause xosview to display a meter that will
shows network usage, with a maximum bandwidth of maxbandwidth. Notice
that setting the bandwidth to 0 no longer disables the meter -- use the
``-net'' option instead.
This option overrides the xosview*page
resource. It is equivalent to setting xosview*page to "False".
+page
This option overrides the xosview*page
resource. It is equivalent to setting xosview*page to "True".
This option overrides the
xosview*pageBandWidth resource. The resource xosview*pageBandWidth will be set
to val.
This option overrides the xosview*disk
resource. It is equivalent to setting xosview*disk to "False".
+disk
This option overrides the xosview*disk
resource. It is equivalent to setting xosview*disk to "True".
This option overrides the xosview*int
resource. It is equivalent to setting xosview*int to "False".
+int
This option overrides the xosview*int
resource. It is equivalent to setting xosview*int to "True".
Equivalent to -int and +int.
This option overrides the xosview*irqrate
resource. It is equivalent to setting xosview*irqrate to
"False".
+irqrate
This option overrides the xosview*irqrate
resource. It is equivalent to setting xosview*irqrate to
"True".
Equivalent to -irqrate and +irqrate.
This option overrides the xosview*lmstemp
resource. It is equivalent to setting xosview*lmstemp to
"False".
+lmstemp
This option overrides the xosview*lmstemp
resource. It is equivalent to setting xosview*lmstemp to
"True".
This switch allows any of xosview's resources
to be set on the command line. An example of how the xosview*memFreeColor
could be set using this option is shown below (Note the use of " to
prevent the shell from expanding ´*´ or from creating two separate
arguments, ´xosview*memfreeColor:´ and ´purple´):
-xrm "xosview*memFreeColor:
purple"
X RESOURCES¶
The following is a list of X resources supported by xosview. Each has a default value assigned to it. These values can be found in the file Xdefaults which can be obtained in the source distribution of xosview. They can be overridden in the usual places (/usr/lib/X11/app-defaults/XOsview, $HOME/.Xdefaults, etc.).The string that xosview will use for the X
window title. Normally xosview will use 'xosview@machine_name' for a title.
This resource overrides the default behavior.
This is a standard X geometry string that
defines the size and location of the X window used by xosview.
The name of the display where xosview will
contact the X server for drawing its window.
The filename of an X pixmap (xpm) file for use
as a background image.
If True then xosview will display meter
captions.
If True then xosview will display meter
labels.
The color to use for the meter labels.
If True then xosview will display labels that
show the percentage of the resource (or absolute amount, depending on the
meter) being used. This option requires that the labels option also be set to
True.
The color to use for "used"
labels.
The width of the border for the xosview
window.
This is the font that xosview will use.
This is the color that will be used for the
background.
This is the color that will be used for the
foreground.
Change to true to try stipple support. This is
primarily for users stuck with 1-bit monitors/display cards. Try setting
enableStipple true. Please give us feedback on this, if you use it. It needs
some more work, but no one has given us any feedback so far.
This defines the number of sample bars drawn
when a meter is in scrolling graph mode. This also has the side-effect of
defining the width of the graph columns. This is only used by meters which
have graph mode enabled.
If True then xosview will display a load
meter.
This is the color that the load meter will use
once the load average is greater than 1.
This is the color that the load meter will use
to display the load average when it is less than or equal to 1.
The load meter will use this color to display
the idle field.
This number (which must be an integer >= 1)
sets the number of tenths of a second that the load meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
This number (which must be an integer >= 1)
sets the value at which the loadmeter changes its status and color from
"normal" to "alarm". The default value is 2.
You should probably leave this at the default
value (False). The load is already a time-averaged value!
If this is set to True then the load meter
will be drawn as a horizontally scrolling bargraph showing the state value
verses time.
This resource tells xosview how to display
"used" labels. The formats work as follows:
float:
Display the value as a floating point
number.
percent:
Display the value as a percentage of the
total.
autoscale:
Display the absolute value and automatically
print the units (K, M, or G) as appropriate.
Display the current CPU speed in the load
meter.
If True then xosview will display a cpu meter.
On linux SMP machines this will cause a separate meter to be displayed for
each cpu if Jerome Forissier's kernel patch has been applied. See the
'README.linux' file for more details. On IRIX 6.5, the resource cpuFormat
decides which meters are created for multiple CPUs.
The cpu meter will use this color to display
the cpu user time field.
The cpu meter will use this color to display
the cpu nice time field.
The cpu meter will use this color to display
the cpu system time field.
The cpu meter will use this color to display
the cpu interrupt time field.
The cpu meter will use this color to display
the cpu idle time field.
This number (which must be an integer >= 1)
sets the number of tenths of a second that the cpu meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
If True then the cpu meter will be split
vertically in two. The top half will show the instantaneous state, while the
bottom half will display a decaying average of the state.
If this is set to True then the cpu meter will
be drawn as a horizontally scrolling bargraph showing the state value verses
time.
This resource tells xosview how to display
"used" labels. The formats work as follows:
float:
Display the value as a floating point
number.
percent:
Display the value as a percentage of the
total.
autoscale:
Display the absolute value and automatically
print the units (K, M, or G) as appropriate.
If `single', only a cumulative meter for all
CPU usage is created. `all' creates a meter for each CPU, but no cumulative
meter. `both' creates one cumulative meter and one for each CPU. `auto' makes
a choice based on the number of CPUs found.
If True then xosview will display a mem
meter.
The mem meter will use this color to display
the used memory field.
The mem meter will use this color to display
the shared memory field.
The mem meter will use this color to display
the buffer memory field.
The mem meter will use this color to display
the cache memory field.
The mem meter will use this color to display
the free memory field.
The mem meter will use this color to display
the shared memory field.
The mem meter will use this color to display
the HP text memory field.
The mem meter will use this color to display
the HP ``other'' memory field.
The mem meter will use this color to display
the NetBSD active memory field.
The mem meter will use this color to display
the NetBSD inactive memory field.
This number (which must be an integer >= 1)
sets the number of tenths of a second that the mem meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
If True then the mem meter will be split
vertically in two. The top half will show the instantaneous state, while the
bottom half will display a decaying average of the state.
If this is set to True then the mem meter will
be drawn as a horizontally scrolling bargraph showing the state value verses
time.
This resource tells xosview how to display
"used" labels. The formats work as follows:
float:
Display the value as a floating point
number.
percent:
Display the value as a percentage of the
total.
autoscale:
Display the absolute value and automatically
print the units (K, M, or G) as appropriate.
If True then xosview will display a swap
meter.
The swap meter will use this color to display
the used swap field.
The swap meter will use this color to display
the free swap field.
This number (which must be an integer >= 1)
sets the number of tenths of a second that the swap meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
If True then the swap meter will be split
vertically in two. The top half will show the instantaneous state, while the
bottom half will display a decaying average of the state.
If this is set to True then the swap meter
will be drawn as a horizontally scrolling bargraph showing the state value
verses time.
This resource tells xosview how to display
"used" labels. The formats work as follows:
float:
Display the value as a floating point
number.
percent:
Display the value as a percentage of the
total.
autoscale:
Display the absolute value and automatically
print the units (K, M, or G) as appropriate.
If True then xosview will display a page
meter.
This number is used to specify the expected
maximum bandwidth (in events / sec) for the page meter. When the expected
maximum bandwidth ( maxEvents) is exceeded then the page meter will
display the relative percentage of page swapping (25% in, 75% out).
The page meter will use this color to display
the page-in field.
The page meter will use this color to display
the page-out field.
The page meter will use this color to display
the idle field.
This number (which must be an integer >= 1)
sets the number of tenths of a second that the page meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
If True then the page meter will be split
vertically in two. The top half will show the instantaneous state, while the
bottom half will display a decaying average of the state.
If this is set to True then the page meter
will be drawn as a horizontally scrolling bargraph showing the state value
verses time.
This resource tells xosview how to display
"used" labels. The formats work as follows:
float:
Display the value as a floating point
number.
percent:
Display the value as a percentage of the
total.
autoscale:
Display the absolute value and automatically
print the units (K, M, or G) as appropriate.
If True xosview will display the GfxMeter. The
value is sampled once per second, due to the usage of sadc to sample
data.
This is the color that the gfx meter will use
once the warn state is reached.
This is the color that the gfx meter will use
once the alarm state is reached.
This is the color that the gfx meter will use
in normal state
The gfx meter will use this color to display
the idle field.
This number (which must be an integer >= 1)
sets the number of tenths of a second that the gfx meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
This number (which must be an integer >= 1)
of swapbuffers per second and pipe at which the gfxmeter changes its status
and color from "normal" to "warn". The default value is
60.
This number (which must be an integer >=
gfxWarnThreshold) of swapbuffers per second and pipe at which the gfxmeter
changes its status and color from "warn" to "alarm". The
default value is 120.
You should probably leave this at the default
value (False). The gfx does not work in decay mode.
If this is set to True then the gfx meter will
be drawn as a horizontally scrolling bargraph showing the state value verses
time.
This resource tells xosview how to display
"used" labels. The formats work as follows:
float:
Display the value as a floating point
number.
percent:
Display the value as a percentage of the
total.
autoscale:
Display the absolute value and automatically
print the units (K, M, or G) as appropriate.
If True xosview will display the NetMeter.
Linux users will have to configure their kernels and setup some ip accounting
rules to make this work. See the file README.linux which comes with the
xosview distribution for details.
This number is used to specify the expected
maximum bandwidth (in bytes / sec) for the meter. When the expected maximum
bandwidth ( maxBytes) is exceeded then the network meter will display
the relative percentage of network usage (25% incoming, 75% outgoing).
If False, xosview will display the data
received/transmitted by any of the network interfaces. Otherwise, xosview will
only display the data received/transmitted by the specified network
interface.
The net meter will use this color to display
the incoming field.
xosview*netOutColor: color
The net meter will use this color to display
the outgoing field.
This is the color that the network meter will
use for the "idle" field.
This number (which must be an integer >= 1)
sets the number of tenths of a second that the net meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
If True then the net meter will be split
vertically in two. The top half will show the instantaneous state, while the
bottom half will display a decaying average of the state.
If this is set to True then the net meter will
be drawn as a horizontally scrolling bargraph showing the state value verses
time.
This resource tells xosview how to display
"used" labels. The formats work as follows:
float:
Display the value as a floating point
number.
percent:
Display the value as a percentage of the
total.
autoscale:
Display the absolute value and automatically
print the units (K, M, or G) as appropriate.
If True then xosview will display a meter to
monitor NFS client stats.
The color to be used for retransmit
stats.
The color to be used for auth refresh
stats.
The color to be used for call stats.
The color to be used for idle stats.
If True xosview will display a meter for NFS
server/daemon stats.
The color to be used for call stats.
The color to be used for bad stats.
The color to be used for UDP stats.
The color to be used for TCP stats.
The color to be used for idle stats.
If True then xosview will display a serial
meter for ttySx. The portbase will be autodetected. Because autodetection can
fail, (if the port is locked by ppp/slip for example) you can specify the
portbase instead of "True". If a portBase is used then xosview will
use it instead of trying to autodetect.
For this to work on Linux xosview needs to be suid root in order to have access
to the ports. See the file README.linux which comes with the xosview
distribution for more details.
This is the color the serial meter will use
for bits that are set.
This is the color the serial meter will use
for bits that are not set.
This number (which must be an integer >= 1)
sets the number of tenths of a second that the serial meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
If True then xosview will display an interrupt
meter.
This is the color that will be used to show
"active" interrupts.
This is the color that will be used to show
"inactive" interrupts.
This number (which must be an integer >= 1)
sets the number of tenths of a second that the int meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
If True then xosview will display a lmstemp
meter.
Highest temp value displayed, default
100.
Color of actual temperature.
Color above alarm temperature, also used to
indicate alarm.
Color between actual and alarm
temperatures.
Name of temperature file from
/proc/sys/dev/sensors/*/*, N=1..
Note if more files with same name exists, only the first is found. There is
currently no possibility to configure equal named files on different busses
(which would be rarely necessary, I hope).
eg.
xosview*lmstemp1: temp xosview*lmstemp2: remote_temp
N-th label for above temperatures, default is
TMP.
This number (which must be an integer >= 1)
sets the number of tenths of a second that the lmstemp meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
This resource tells xosview how to display
"used" labels. The formats work as follows:
float:
Display the value as a floating point
number.
percent:
Display the value as a percentage of the
total.
autoscale:
Display the absolute value and automatically
print the units (K, M, or G) as appropriate.
If True then xosview will display a battery
meter. Linux users will need to have APM or ACPI support in their kernels for
this to work. For both, APM and ACPI xosview shows the status/sum of all
batteries. Additionally - the legend text gets changed/adjusted to reflect the
current state (charging/low/critical/etc.) of the battery/batteries.
This is the color that will be used to show
the amount of battery power left.
This is the color that will be used to show
the amount of battery power used.
This is the color that will be used as 'left'
- if the batteries get charged.
This is the color that will be used as 'left'
- if the batteries are fully charged. APM and ACPI does provide this info, but
not all machines actually do so.
APM only - the 'left' color that will indicate
a low battery. Depends on the machine - e.g. below 25% remaining
capacity.
APM case: the 'left' color if APM indicates
'critical' state. (less than 5%)
ACPI case: the 'left' color if the remaining capacity is below the alarm value.
(which can be set by the user in /proc/acpi/battery/BAT[01]/alarm )
If no battery is present - or all batteries
get removed (while on AC).
This number (which must be an integer >= 1)
sets the number of tenths of a second that the battery meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
This resource tells xosview how to display
"used" labels. The formats work as follows:
float:
Display the value as a floating point
number.
percent:
Display the value as a percentage of the
total.
autoscale:
Display the absolute value and automatically
print the units (K, M, or G) as appropriate.
If True then xosview will display the
link-Quality of wireless connections. Note that the graph will *never* schow
up, if you don't have any wireless Devices, or no wireless extensions in
Kernel (/proc/net/wireless). Default is true.
This is the color for the Link-Graph with
Quality between 0 and 6.
This is the color for the Link-Graph with
Quality between 7 and 14.
This is the color for the Link-Graph with
Quality higher than 14.
This is the background color.
This number (which must be an integer >= 1)
sets the number of tenths of a second that the wireless meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
If True then the wireless meter will be split
vertically in two. The top half will show the instantaneous state, while the
bottom half will display a decaying average of the state.
This resource tells xosview how to display
"used" labels. The formats work as follows:
float:
Display the value as a floating point
number.
percent:
Display the value as a percentage of the
total.
autoscale:
Display the absolute value and automatically
print the units (K, M, or G) as appropriate.
If True then xosview will display a disk
meter.
The disk meter will use this color to display
the bytes transferred (in or out) field.
The disk meter will use this color to display
the idle field.
This number is used to specify the expected
maximum bandwidth in bytes per second for the disk meter.
This color will be used for the linux meter to
show writes.
This color will be used for the linux meter to
show reads.
This number (which must be an integer >= 1)
sets the number of tenths of a second that the disk meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
If True then the disk meter will be split
vertically in two. The top half will show the instantaneous state, while the
bottom half will display a decaying average of the state.
If this is set to True then the disk meter
will be drawn as a horizontally scrolling bargraph showing the state value
verses time.
This resource tells xosview how to display
"used" labels. The formats work as follows:
float:
Display the value as a floating point
number.
percent:
Display the value as a percentage of the
total.
autoscale:
Display the absolute value and automatically
print the units (K, M, or G) as appropriate.
If True then xosview will display a RAID
meter.
Please enter your RAID device count (n) here
or 0 if you don't have any supported RAID devices. xosview then will display n
RAID state displays.
These colors will be used for indicating
working/online or failed/offline disks. The order (from left to right) is the
same as in /proc/mdstat.
If a resync/rebuild of the RAID array is in
progress, the "done" and "todo" colors will be used. If no
rebuild/resync is running, then the "complete" color will be
shown.
This number (which must be an integer >= 1)
sets the number of tenths of a second that the RAID meter waits between
updates. A value of 1 has xosview update the meter 10 times per second (the
fastest). A value of 600 would cause xosview to update the meter once a
minute.
This resource tells xosview how to display
"used" labels. The formats work as follows:
float:
Display the value as a floating point
number.
percent:
Display the value as a percentage of the
total.
autoscale:
Display the absolute value and automatically
print the units (K, M, or G) as appropriate.
OBTAINING¶
This version of xosview is distributed from the following site:AUTHORS¶
Mike Romberg <mike.romberg@noaa.gov>Original author, Linux and HPUX ports.
NetBSD port and most of the nice enhancements
for version 1.4, initial work on FreeBSD port.
Added the scrolling graph mode.
Most of the FreeBSD support, more
resource-handling improvements.
SunOS port.
IRIX 6.5 port.
FreeBSD libdevstat-based diskmeter
support.
Added battery-meter support to NetBSD.
OpenBSD interrupt-meter support.
Originator of the loadmeter.
Linux pagemeter.
Made extensions to the serial-meter.
Ported the linux memstat kernel module to
linux-2.1
Author of the Linux SMP kernel patch which
xosview uses to display meters for each CPU.
Initial port to BSDI.
Solaris disk and network meters.
Fixes for linux diskmeter + ip_chains
support
Linux raid meter, bitfieldmeter. Many cosmetic
fixes.
Linux lms temp meter.
FreeBSD 4.* updates, and a few other
suggestions.
C++ standard compliance and other NetBSD
fixes.
Wireless Link-Meter for Linux.
Bug fixes and general caretaking.
3rd Berkeley Distribution |