xosview (1)
NAME
xosview - X based system monitorSYNOPSIS
xosview [options]DESCRIPTION
xosview is a monitor which displays the status of several system 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 is being put to a particular use.xosview runs on several platforms (Linux, NetBSD, FreeBSD, OpenBSD, DragonflyBSD, some Solaris systems, IRIX 6.5, HPUX and GNU). Not all of the meters described below are supported on all platforms. Some of the meters may appear different depending upon the platform xosview is running on. Note that *BSD is used as an abbreviation for all the supported BSD operating systems (NetBSD, FreeBSD, OpenBSD, DragonflyBSD).
Load: Kernel reported load average
all platforms : load
Linux : load | CPU frequency
*BSD : load | CPU frequency
SunOS5 : load | CPU frequency
CPU Usage
Linux : user | nice | system | soft-interrupt | interrupt | io-wait |
guest | niced guest | stolen | idle
*BSD : user | nice | system | interrupt | idle
SunOS5 : user | system | wait | idle
IRIX : user | system | interrupt | wait | idle
HPUX : user | nice | system | interrupt | idle
Memory Usage
Linux : used | buffers | slab | map | cache | free
FreeBSD: active | inactive | wired | cache | free
DFBSD : active | inactive | wired | cache | free
OpenBSD: active | inactive | wired | free
NetBSD : active | inactive | wired | free
SunOS5 : kernel | zfs | other | free
IRIX : kernel | fs | user | free
HPUX : text | used | other | free
GNU : active | inactive | wired | free
Swap Usage
Linux : used | free
*BSD : used | free
SunOS5 : used | free
HPUX : used | free
GNU : used | free
Disk Usage: Throughput to/from local disk, per second
Linux : in | out | idle
*BSD : in | out | idle
SunOS5 : in | out | idle
Page Swapping: Pages to/from swap, per second
Linux : in | out | idle
*BSD : in | out | idle
SunOS5 : in | out | idle
HPUX : in | out | idle
GNU : in | out | idle
Network Usage
Linux : in | out | idle
*BSD : in | out | idle
SunOS5 : in | out | idle
GFX Usage: Framebuffer exchanges, per second
IRIX : swapbuffers
Interrupts: "leds" which blink when an interrupt occurs
Linux : IRQs
*BSD : IRQs
Interrupt Rate: Per second
Linux : interrupts | free
*BSD : interrupts | free
SunOS5 : interrupts | free
Serial Port Status: "leds" which show the serial port parameters
Linux : LSR and MSR
Battery Level: charge and status of batteries
Linux : available | used
*BSD : available | used
RAID: State of disks in a software RAID array
Linux : disk0 disk1 disk2 ... diskN | rebuild
Wireless Link
Linux : quality
Sensors: Readings from sensors
Linux : I2C/hwmon sensors (lmstemp)
Intel Core/AMD K8+/VIA C7 temperature (coretemp)
ACPI thermal zones (acpitemp)
*BSD : I2C sensors (bsdsensor)
Intel Core/AMD K8+ temperature (coretemp)
Typing a 'q' in the window will terminate xosview.
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.
-v
- Displays the version number.
-name name
-
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 &
-
-display display
- Sets the X display to display. This option overrides the xosview*display resource.
-font font
- Specifies the font xosview will use for labels. This option overrides the xosview*font resource.
-title title
- 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.
-geometry geometry_string
- Sets the X geometry to geometry_string. This option overrides the xosview*geometry resource.
-captions
- This option overrides the xosview*captions resource. is equivalent to setting xosview*captions to "False".
+captions
- This option overrides the xosview*captions resource. is equivalent to setting xosview*captions to "True".
- This option overrides the xosview*labels resource. is equivalent to setting xosview*labels to "False".
+labels
- This option overrides the xosview*labels resource. is equivalent to setting xosview*labels to "True".
- This option overrides the xosview*usedlabels resource. is equivalent to setting xosview*usedlabels to "False".
+usedlabels
- This option overrides the xosview*usedlabels resource. is equivalent to setting xosview*usedlabels to "True".
- This option overrides the xosview*cpu resource. is equivalent to setting xosview*cpu to "False".
+cpu
- This option overrides the xosview*cpu resource. is equivalent to setting xosview*cpu to "True".
-cpus
- Force the display of a single meter for all CPUs in the system. This option is equivalent to setting xosview*cpuFormat to "single".
+cpus
- Force the display of all CPUs in the system. This option is equivalent to setting xosview*cpuFormat to "all".
-load
- This option overrides the xosview*load resource. is equivalent to setting xosview*load to "False".
+load
- This option overrides the xosview*load resource. is equivalent to setting xosview*load to "True".
- This option overrides the xosview*mem resource. is equivalent to setting xosview*mem to "False".
+mem
- This option overrides the xosview*mem resource. is equivalent to setting xosview*mem to "True".
- This option overrides the xosview*swap resource. is equivalent to setting xosview*swap to "False".
+swap
- This option overrides the xosview*swap resource. is equivalent to setting xosview*swap to "True".
- This option overrides the xosview*battery resource. is equivalent to setting xosview*battery to "False".
+battery
- This option overrides the xosview*battery resource. is equivalent to setting xosview*battery to "True".
- This option overrides the xosview*gfx resource. is equivalent to setting xosview*gfx to "False".
+gfx
- This option overrides the xosview*gfx resource. is equivalent to setting xosview*gfx to "True".
- This option overrides the xosview*wireless resource. is equivalent to setting xosview*wireless to "False".
+wireless
- This option overrides the xosview*wireless resource. is equivalent to setting xosview*wireless to "True".
- This option overrides the xosview*net resource. is equivalent to setting xosview*net to "False".
+net
- This option overrides the xosview*net resource. is equivalent to setting xosview*net to "True".
-network maxbandwidth -networkBW maxbandwidth -networkBandwidth maxbandwidth
- 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.
-page
- This option overrides the xosview*page resource. is equivalent to setting xosview*page to "False".
+page
- This option overrides the xosview*page resource. is equivalent to setting xosview*page to "True".
-pagespeed val
- This option overrides the xosview*pageBandWidth resource. The resource xosview*pageBandWidth will be set to val.
-disk
- This option overrides the xosview*disk resource. is equivalent to setting xosview*disk to "False".
+disk
- This option overrides the xosview*disk resource. is equivalent to setting xosview*disk to "True".
- This option overrides the xosview*int resource. is equivalent to setting xosview*int to "False".
+int
- This option overrides the xosview*int resource. is equivalent to setting xosview*int to "True".
-ints +ints -interrupts +interrupts
- Equivalent to -int and +int.
-irqrate
- This option overrides the xosview*irqrate resource. is equivalent to setting xosview*irqrate to "False".
+irqrate
- This option overrides the xosview*irqrate resource. is equivalent to setting xosview*irqrate to "True".
-intrate +intrate
- Equivalent to -irqrate and +irqrate.
-lmstemp
- This option overrides the xosview*lmstemp resource. is equivalent to setting xosview*lmstemp to "False".
+lmstemp
- This option overrides the xosview*lmstemp resource. is equivalent to setting xosview*lmstemp to "True".
- This option overrides the xosview*coretemp resource. is equivalent to setting xosview*coretemp to "False".
+coretemp
- This option overrides the xosview*coretemp resource. is equivalent to setting xosview*coretemp to "True".
- This option overrides the xosview*acpitemp resource. is equivalent to setting xosview*acpitemp to "False".
+acpitemp
- This option overrides the xosview*acpitemp resource. is equivalent to setting xosview*acpitemp to "True".
- This option overrides the xosview*bsdsensor resource. is equivalent to setting xosview*bsdsensor to "False".
+bsdsensor
- This option overrides the xosview*bsdsensor resource. is equivalent to setting xosview*bsdsensor to "True".
-xrm resource_string
-
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.).
It should be noted that it is OK to have a resource defined for a port of xosview that does not support the feature the resource configures. Xosview will simply ignore the resources that are set for it but not supported on a given platform.
General Resources
xosview*title: name
- 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.
xosview*geometry: geometry_string
- This is a standard X geometry string that defines the size and location of the X window used by xosview.
xosview*display: name
- The name of the display where xosview will contact the X server for drawing its window.
xosview*pixmapName: name
- The filename of an X pixmap (xpm) file for use as a background image.
xosview*captions: (True or False)
- If True then xosview will display meter captions.
xosview*labels: (True or False)
- If True then xosview will display meter labels.
xosview*meterLabelColor: color
- The color to use for the meter labels.
xosview*usedlabels: (True or False)
- 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.
xosview*usedLabelColor: color
- The color to use for "used" labels.
xosview*borderwidth: width
- The width of the border for the xosview window.
xosview*font: font
- This is the font that xosview will use.
xosview*background: color
- This is the color that will be used for the background.
xosview*foreground: color
- This is the color that will be used for the foreground.
xosview*enableStipple: (True or False)
- 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.
xosview*graphNumCols: number
- 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.
Load Meter Resources
xosview*load: (True or False)
- If True then xosview will display a load meter.
xosview*loadProcColor: color
- This is the color that the load meter will use to display the load average when it is below the warning threshold.
xosview*loadWarnColor: color
- This is the color that the load meter will use once the load average is above the warning but below the critical load threshold.
xosview*loadCritColor: color
- This is the color that the load meter will use once the load average is above critical load threshold.
..pp load
xosview*loadWarnThreshold: int .RS This number (which must be an integer >= 1) sets the value at which the loadmeter changes its status and color from "normal" to "warning". The default value is the number of processors. .RE
xosview*loadCritThreshold: int .RS This number (which must be an integer >= 1) sets the value at which the loadmeter changes its status and color from "warning" to "critical". The default value is four times the warning threshold. .RE
xosview*loadDecay: (True or False) .RS You should probably leave this at the default value (False). The load is already a time-averaged value! .RE
.dg load
..uf load
xosview*loadCpuSpeed: (True or False) .RS Display the current CPU speed in the load meter. .RE
CPU Meter Resources
xosview*cpu: (True or False) .RS If True then xosview will display a cpu meter. On Linux, *BSD, Solaris and IRIX SMP machines, the resource cpuFormat defines how meters are created for multiple CPUs. .RE
..cc cpu User "cpu user time"
.cc cpu Nice "cpu nice time"
.cc cpu System "cpu system time"
.cc cpu Interrupt "cpu hard interrupt time"
.cc cpu SInterrupt "cpu soft interrupt time"
.cc cpu Wait "cpu IO waiting time"
.cc cpu Guest "cpu virtualization guest time"
.cc cpu NiceGuest "cpu niced virtualization guest time"
.cc cpu Stolen "cpu involuntary wait time"
.cc cpu Free "cpu idle time"
..pp cpu
.dc cpu
.dg cpu
.uf cpu
xosview*cpuFormat: (single, all, both or auto) .RS 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. .RE
xosview*cpuFields: USED/USR/NIC/SYS/INT/SI/HI/WIO/GST/NGS/STL/IDLE .RS The set of fields to show in Linux CPU meter instead of the default. Possible fields are:
USED: .RS Combine all used CPU time into one field. This is the sum of user, nice, system, soft and hard interrupts, guest, niced guest and stolen times. None of these, except stolen, may be defined together with `USED'. .RE IDLE: .RS Time spent doing nothing. Includes I/O wait if it is not defined separately. .RE USR: .RS Time spent in user mode processes. Includes nice, guest and niced guest if those are not defined separately. .RE NIC: .RS Time spent in niced user mode processes. Includes niced guest if neither it nor guest is not defined separately. .RE SYS: .RS Time spent in kernel code. Includes soft and hard interrupt as well as stolen time if those are not defined separately. .RE INT: .RS Combines soft and hard interrupt handling times into one field. .RE SI: .RS Time the kernel used to handle soft interrupts. Available on Linux kernel 2.6.0 and higher. .RE HI: .RS Time the kernel used to handle hard interrupts. Available on Linux kernel 2.6.0 and higher. .RE WIO: .RS Time spent waiting for I/O to complete. Available on Linux kernel 2.6.0 and higher. .RE GST: .RS Time spent running guest OS in virtual machine. Includes niced guest if it is not defined separately. Available on Linux kernel 2.6.24 and higher. .RE NGS: .RS Time spent running niced guest OS in virtual machine. Available on Linux kernel 2.6.32 and higher. .RE STL: .RS Involuntary wait time when running as guest in virtual machine. Available on Linux kernel 2.6.11 and higher. .RE
Most combinations are possible (see above for restrictions), but at least `USED' or `USR' and `SYS' need to be defined. `IDLE' field is added automatically. .RE
Memory Meter Resources
..xt mem
..cc mem Used "used memory"
.cc mem Shared "shared memory"
.cc mem Buffer "buffer memory"
.cc mem Cache "cache memory"
.cc mem Free "free memory"
.cc mem Kernel "kernel memory"
.cc mem Shared "shared memory"
.cc mem Text "HP text memory"
.cc mem Other "HP ``other'' memory"
.cc mem Active "*BSD active memory"
.cc mem Inactive "*BSD inactive memory"
.cc mem Wired "*BSD wired memory"
.cc mem Slab "Linux in-kernel data structures"
.cc mem Map "Linux memory mapped files"
..pp mem
.dc mem
.dg mem
.uf mem
Swap Meter Resources
..xt swap
..cc swap Used "used swap"
.cc swap Free "free swap"
..pp swap
.dc swap
.dg swap
.uf swap
Page Swapping Meter Resources
..xt page
xosview*pageBandWidth: maxEvents .RS 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). .RE
..cc page In page-in
.cc page Out page-out
.cc page Idle idle
..pp page
.dc page
.dg page
.uf page
Gfx Meter Resources
xosview*gfx: (True or False)
.RS If True xosview will display the GfxMeter. The value is sampled once per second, due to the usage of sadc to sample data. .RE
xosview*gfxWarnColor: color .RS This is the color that the gfx meter will use once the warn state is reached. .RE
xosview*gfxAlarmColor: color .RS This is the color that the gfx meter will use once the alarm state is reached. .RE
xosview*gfxSwapColor: color .RS This is the color that the gfx meter will use in normal state .RE
..cc gfx Idle idle
..pp gfx
xosview*gfxWarnThreshold: int .RS 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. .RE
xosview*gfxAlarmThreshold: int .RS 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. .RE
xosview*gfxDecay: (True or False) .RS You should probably leave this at the default value (False). The gfx does not work in decay mode. .RE
.dg gfx
..uf gfx
Network Meter Resources
xosview*net: (True or False) .RS 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. .RE
xosview*netBandwidth: maxBytes .RS 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). .RE
xosview*netIface: interface .RS 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. If the name is prepended with '-' sign, the data in that interface is ignored. .RE
..cc net In incoming
.cc net Out outgoing .
xosview*netBackground: color .RS This is the color that the network meter will use for the "idle" field. .RE
..pp net
.dc net
.dg net
.uf net
NFSStats (Client) Resources
xosview*NFSStats: (True or False) .RS If True then xosview will display a meter to monitor NFS client stats. .RE
xosview*NFSStatReTransColor: color .RS The color to be used for retransmit stats. .RE
xosview*NFSStatAuthRefrshColor: color
.RS The color to be used for auth refresh stats. .RE
xosview*NFSStatCallsColor: color .RS The color to be used for call stats. .RE
xosview*NFSStatIdleColor: color .RS The color to be used for idle stats. .RE
NFSDStats (Server) Resources
xosview*NFSDStats: (True or False) .RS If True xosview will display a meter for NFS server/daemon stats. .RE
xosview*NFSDStatCallsColor: color .RS The color to be used for call stats. .RE
xosview*NFSDStatBadCallsColor: color .RS The color to be used for bad stats. .RE
xosview*NFSDStatUDPColor: color .RS The color to be used for UDP stats. .RE
xosview*NFSDStatTCPColor: color .RS The color to be used for TCP stats. .RE
xosview*NFSDStatIdleColor: color .RS The color to be used for idle stats. .RE
Serial Meter Resources
xosview*serial(0-9): (True, False, or portBase) .RS 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. .RE
xosview*serialOnColor: color .RS This is the color the serial meter will use for bits that are set. .RE
xosview*serialOffColor: color .RS This is the color the serial meter will use for bits that are not set. .RE
..pp serial
Interrupt Meter Resources
xosview*interrupts: (True or False) .RS If True then xosview will display an interrupt meter. .RE
xosview*intSeparate: (True of False) .RS If True then xosview will display one interrupt meter per CPU on SMP machines. If False only one meter is displayed. Default: True. .RE
xosview*intOnColor: color .RS This is the color that will be used to show "active" interrupts. .RE
xosview*intOffColor: color .RS This is the color that will be used to show "inactive" interrupts. .RE
..pp int
Interrupt Rate Meter Resources
xosview*irqrate: (True or False) .RS If True then xosview will display an interrupt rate meter. .RE
xosview*irqrateUsedColor: color .RS This is the color that will be used to show the interrupt rate. .RE
.cc irqrate Idle idle
..pp irqrate
.dc irqrate
.dg irqrate
.uf irqrate
Lm Sensors Resources
.xt lmstemp
xosview*lmstempHighest: number .RS Highest value displayed. If not given, or too small, the meter will adjust to fit actual and alarm values. Can be overridden for any meter with .RE
xosview*lmstempActColor: color .RS Color of actual value. .RE
xosview*lmstempHighColor: color .RS Color above high alarm value, also used to indicate alarm. .RE
xosview*lmstempLowColor: color .RS Color of actual value, when it is below low alarm value. .RE
xosview*lmstempIdleColor: color .RS Color between actual and high alarm values. .RE
xosview*lmstempN: filename .RS Name of input file from /proc/sys/dev/sensors/*/* or /sys/class/hwmon/*/{,device}/, N=1,2,3,... Can also be absolute path. For example, .br xosview*lmstemp1: temp1 .br xosview*lmstemp2: temp2_input .br
Note: Many sensors have the value and alarm threshold in files named "*_input" and "*_max"/"*_min", respectively. In such case, specifying the base name such as "temp1" here will be enough for having both files used. .br
Note: If the same file name as lmstempN, lmshighN or be specified, or absolute path used, to find the correct one. .RE
xosview*lmshighN: filename or number .RS Optional high alarm value or name of file from /sys/class/hwmon/*/{,device}/, N=1,2,3,... Can also be absolute path. If not given, lmstempHighest is used as both maximum and high alarm. For example, .br xosview*lmshigh1: 70 .br xosview*lmshigh2: temp1_crit_hyst .RE
xosview*lmslowN: filename or number .RS Optional low alarm value or name of file from /sys/class/hwmon/*/{,device}/, N=1,2,3,... Can also be absolute path. Default is 0. For example, .br xosview*lmslow1: 1.5 .br xosview*lmslow2: fan1_min .RE
xosview*lmsnameN: name .RS Optional name of the sensor device to use when finding the filename(s) given in /sys/class/hwmon/*/{,device}/name for the names of your sensors. This has no effect to files given as absolute paths. For example, .br xosview*lmsname1: nct6779 .br xosview*lmsname2: radeon .RE
xosview*lmstempLabelN: string .RS N-th label for above values, default is TMP. .RE
xosview*lmstempHighestN: number .RS Override default lmstempHighest for meter N. .RE
xosview*lmstempUsedFormatN: (float, percent or autoscale) .RS Override default lmstempUsedFormat for meter N. .RE
.pp lmstemp
.uf lmstemp
ACPI Temperature Resources
.xt acpitemp
xosview*acpitempHighest: 100 .RS Highest temp value displayed, default 100. If acpihighN is given, the value is read from there instead. .RE
xosview*acpitempActColor: color .RS Color of actual temperature. .RE
xosview*acpitempHighColor: color .RS Color above alarm temperature, also used to indicate alarm. .RE
xosview*acpitempIdleColor: color .RS Color between actual and alarm temperatures. .RE
xosview*acpitempN: filename .RS Name of temperature file from /proc/acpi/thermal_zone or /sys/devices/virtual/thermal. Note that the last directory part must be given, e.g. TZ0/temperature. Absolute path can also be used. .RE
xosview*acpihighN: filename .RS Name of high value/trip point file from /proc/acpi/thermal_zone or /sys/devices/virtual/thermal, or an absolute path to one. .RE
xosview*acpitempLabelN: Labelstring .RS N-th label for above temperatures, default is TMP. .RE
.pp acpitemp
.uf acpitemp
Intel Core / AMD K8+ / VIA C7 Temperature Sensor Resources
.xt coretemp
xosview*coretempHighest: 100 .RS Highest temp value displayed, default 100. If CPU throttling temperature (tjMax) is supplied by the operating system, it is used instead. .RE
xosview*coretempHigh: number .RS Value to use as alarm temperature, default is coretempHighest. If a usable value, such as the temperature for which maximum cooling is required, is supplied by the operating system, it is used instead. .RE
xosview*coretempActColor: color .RS Color of actual temperature. .RE
xosview*coretempHighColor: color .RS Color above alarm temperature, also used to indicate alarm. .RE
xosview*coretempIdleColor: color .RS Color between actual and alarm temperatures. .RE
xosview*coretempDisplayType: (separate, average or maximum) .RS This resource tells xosview how to display the CPU temperature. The formats work as follows:
separate: .RS Display one meter for each CPU core of a multi-core CPU. This is the default. .RE average: .RS Display the average of core temperatures of a multi-core CPU. On multi-socket machines, one meter per physical CPU is displayed. .RE maximum: .RS Display the highest core temperature of a multi-core CPU. On multi-socket machines, one meter per physical CPU is displayed. .RE .RE
.pp coretemp
.uf coretemp
*BSD Sensor Resources
.xt bsdsensor
xosview*bsdsensorHighest: number .RS Highest value displayed. If not given, or too small, the meter will adjust to fit actual and alarm values. Can be overridden for any meter with bsdsensorHighestN. .RE
xosview*bsdsensorActColor: color .RS Color of actual value. .RE
xosview*bsdsensorHighColor: color .RS Color above high alarm value, also used to indicate alarm. .RE
xosview*bsdsensorLowColor: color .RS Color of actual value, when it is below low alarm value. .RE
xosview*bsdsensorIdleColor: color .RS Color between actual and high alarm values. .RE
xosview*bsdsensorN: name.type .br xosview*bsdsensorHighN: name.type .br xosview*bsdsensorLowN: name.type .RS These define where the actual value, high alarm value and low alarm value for meter N=1,2,3,... will be read from. The name is the sensor driver, and type is the wanted value. Both alarm values are optional, and can also be given as static numerical values. .br
You can find the correct pair for OpenBSD and DragonFly BSD with systat command, e.g. .br xosview*bsdsensor1: it0.temp1 .br xosview*bsdsensorHigh1: 100
On NetBSD, you can find the driver name with envstat command. Value name for the actual reading is typically 'cur-value' and for high alarm 'critical-max' and for low alarm 'critical-min', e.g. .br xosview*bsdsensor2: coretemp0.cur-value .br xosview*bsdsensorHigh2: coretemp0.critical-max
For all possible NetBSD value names, refer to envstat source code.
FreeBSD has no usable sensor drivers as of version 9.0. However, ACPI thermal zones can be used by defining the sysctl node below hw.acpi.thermal, e.g. .br xosview*bsdsensor1: tz0.temperature .br xosview*bsdsensorHigh1: tz0._CRT .br
ACPI thermal zones can be used like this on DragonFly BSD as well. .RE
xosview*bsdsensorLabelN: string .RS N-th label for above meters, default is SENN. .RE
xosview*bsdsensorHighestN: number .RS Override default bsdsensorHighest for meter N. .RE
xosview*bsdsensorUsedFormatN: (float, percent or autoscale) .RS Override default bsdsensorUsedFormat for meter N. .RE
.pp bsdsensor
.uf bsdsensor
Battery Meter Resources
xosview*battery: (True or False) .RS 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. .RE
xosview*batteryLeftColor: color .RS This is the color that will be used to show the amount of battery power left. .RE
xosview*batteryUsedColor: color .RS This is the color that will be used to show the amount of battery power used. .RE
xosview*batteryChargeColor: color .RS This is the color that will be used as 'left' - if the batteries get charged. .RE
xosview*batteryFullColor: color .RS 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. .RE
xosview*batteryLowColor: color .RS APM only - the 'left' color that will indicate a low battery. Depends on the machine - e.g. below 25% remaining capacity. .RE
xosview*batteryCritColor: color .RS 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 ) .RE
xosview*batteryNoneColor: color .RS If no battery is present - or all batteries get removed (while on AC). .RE
..pp battery
.uf battery
Wireless Meter Resources
xosview*wireless: (True or False) .RS If True then xosview will display the link quality of each wireless connection. Note that the graph will *never* show up, if you don't have any wireless devices, or no wireless extensions in the kernel (/proc/net/wireless). Default is true. .RE
xosview*PoorQualityColor: color .RS This is the color for the quality field when between 0 and 6. .RE
xosview*FairQualityColor: color .RS This is the color for the quality field when between 7 and 14. .RE
xosview*GoodQualityColor: color .RS This is the color for the quality field when higher than 14. .RE
xosview*wirelessUsedColor: color .RS This is the background color. .RE
..pp wireless
.dc wireless
.uf wireless
Disk Meter Resources
..xt disk
..cc disk In reads
.cc disk Out writes
.cc disk Idle idle
xosview*diskBandwidth: bandwidth .RS This number is used to specify the expected maximum bandwidth in bytes per second for the disk meter. .RE
xosview*diskWriteColor: color .RS This color will be used for the linux meter to show writes. .RE
xosview*diskReadColor: color .RS This color will be used for the linux meter to show reads. .RE
..pp disk
.dc disk
.dg disk
.uf disk
RAID Meter Resources
..xt RAID
xosview*RAIDdevicecount: int .RS 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. .RE
xosview*RAIDdiskOnlineColor: color
xosview*RAIDdiskFailureColor: color .RS 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. .RE
xosview*RAIDresyncdoneColor: color
xosview*RAIDresynctodoColor: color
xosview*RAIDresynccompleteColor: color .RS 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. .RE
..pp RAID
..uf RAID
.SH OBTAINING
This version of xosview is distributed from the following site:
.RS www.pogo.org.uk/~mark/xosview .RE
.SH AUTHORS
Mike Romberg <mike.romberg@noaa.gov> .RS Original author, Linux and HPUX ports. .RE
Brian Grayson <bgrayson@netbsd.org> .RS NetBSD port and most of the nice enhancements for version 1.4, initial work on FreeBSD port. .RE
Scott McNab <jedi@tartarus.uwa.edu.au> .RS Added the scrolling graph mode. .RE
Tom Pavel <pavel@slac.stanford.edu> .RS Most of the FreeBSD support, more resource-handling improvements. .RE
Greg Onufer <exodus@cheers.bungi.com> .RS SunOS port. .RE
Stefan Eilemann <eilemann@gmail.com> .RS IRIX 6.5 port. .RE
Sheldon Hearn <axl@iafrica.com> .RS FreeBSD libdevstat-based diskmeter support. .RE
David W. Talmage <talmage@jefferson.cmf.nrl.navy.mil> .RS Added battery-meter support to NetBSD. .RE
Oleg Safiullin <form@openbsd.org> .RS OpenBSD interrupt-meter support. .RE
Werner Fink <werner@suse.de> .RS Originator of the loadmeter. .RE
Massimiliano Ghilardi <ghilardi@cibs.sns.it> .RS Linux pagemeter. .RE
Carsten Schabacker <cschaba@spock.central.de> .RS Made extensions to the serial-meter. .RE
Paal Beyer <pbeyer@online.no> .RS Ported the linux memstat kernel module to linux-2.1 .RE
Jerome Forissier <forissier@isia.cma.fr> .RS Author of the Linux SMP kernel patch which xosview uses to display meters for each CPU. .RE
Tomer Klainer <mandor@cs.huji.ac.il> .RS Initial port to BSDI. .RE
Arno Augustin <Arno.Augustin@3SOFT.de> .RS Solaris disk and network meters. .RE
Alberto BARSELLA <ishark@lsh01.univ-lille1.fr> .RS Fixes for linux diskmeter + ip_chains support .RE
Thomas Waldmann <ThomasWaldmann@gmx.de> .RS Linux raid meter, bitfieldmeter. Many cosmetic fixes. .RE
Leopold Toetsch <lt@toetsch.at> .RS Linux lms temp meter. .RE
David O'Brien <obrien@nuxi.com> .RS FreeBSD 4.* updates, and a few other suggestions. .RE
Christos Zoulas <christos@netbsd.org> .RS C++ standard compliance and other NetBSD fixes. .RE
Tim Ehlers <tehlers@gwdg.de> .RS Wireless Link-Meter for Linux. .RE
Mark Hills <mark@pogo.org.uk> .RS Bug fixes and general caretaking. .RE
Tomi Tapper <tomi.o.tapper@student.jyu.fi> .RS Temperature sensor, and FreeBSD updates. .RE
Raymond S Brand (rsbx@acm.org) .RS Misc fixes. .RE
And many others who have sent in small fixes and improvements.