![]() |
![]()
| ![]() |
![]()
NAMExcpustate - display CPU states (idle, nice, system, kernel) statisticsSYNTAXxcpustate [ -toolkitoption ...] [ -count iterations] [ -interval seconds] [ -shorten components] [ -cpu] [ -nocpu] [ -disk] [ -nodisk] [ -omni] [ -noomni] [ -wait] [ -nowait] [ -filltype auto|grayscale|color|tile|stipple] [ -host hostname] [ -version] [ -colors colorname[,colorname[,...]]] [ -avg iterations][ -kernel pathname] [ -mmap] [ -nommap]DESCRIPTIONXcpustate displays bars showing the percentage of time the CPU spends in different states. On some systems, it optionally indicates disk states in the same manner. It can also query remote systems that offer RSTAT RPC services.When using the RSTAT protocol, or when running locally on machines running Cygwin, or Berkeley Unix or a derivative (eg. suns with SunOS<=4.1.1, microVaxen with Ultrix), the bar indicates the proportions of idle, user, nice, and system time with increasing levels of grayscale or color (from left to right). When running locally on supported multiprocessors (Solbourne OS/MP systems, Ultrix multiprocessors, Linux/SMP, and the Gould NP1), there will be one bar for each CPU. On Linux systems, each CPU bar indicates the proportions of idle, user, nice, and system time, respectively, from left to right. Each disk drive bar indicates the proportions of idle, read I/O operations, and write I/O operations, from left to right. For disk drive bars, the I/O operations are displayed on a sliding scale, the entire bar corresponding to the maximum total (read and write) number of I/O operations per interval since xcpustate was started, and read/write I/O operations shown as fractions of the current maximum. For disk drive bar display under Linux, xcpustate relies on the "disk_io" statistics in /proc/stat (2.4 kernels) or the information in /proc/diskstats (2.6 or later kernels). On systems running OpenBSD 3.0 or later, each CPU bar indicates the proportions of idle, user, nice, interrupt, and system time, respectively, from left to right. On an SGI system running IRIX, there will be one bar for each CPU, indicating the proportions of idle + wait, user, kernel, sxbrk and interrupt time for that CPU. If the ``wait'' option is set, the bars indicate idle, wait, user, kernel, sxbrk, and interrupt time, from left to right. On a Sun multiprocessor under SunOS 4.1.2 or 4.1.3, bars indicate the proportions of idle + diskwait, user, nice, system, spinlock, and crosscall service time for each CPU. On a Sun or other system (eg. Solbourne, Cray Superserver-6400) running Solaris 2.x or later, and on an IBM system running AIX, bars indicate the proportions of idle + wait, user, and kernel time for each CPU. If the ``wait'' option is set, the bars indicate idle, wait, user, and system/kernel time, from left to right. On a Cray X/MP or Y/MP running Unicos 5.1 or greater, bars indicate the proportions of idle + wait, user and system/kernel time for each CPU. On systems running the Mach operating system, bars indicates the proportions of user, system, and idle time for each CPU. On supported SVR4 systems (e.g. Dell Unix 2.2), a single bar is displayed showing idle, user, system and wait times. On NCR SVR4 MP/RAS systems, one bar for each CPU (or disk drive) is displayed. Each bar indicates the relative proportions of idle, user, system and wait times for that CPU. Disk drive times show device idle and busy. OPTIONSXcpustate accepts all of the standard X Toolkit command line options, plus:
X DEFAULTSFor xcpustate the available class identifiers are:CPUStateMonitor - the application Form - enclosing the entire application, and sub-Forms enclosing Label/Bar pairs. For xcpustate, the available name identifiers are: xcpustate - application name The outer Form is "form". The Forms enclosing the Label/Bar pairs are "formN", where N is the index number, starting with the top pair as zero. Each Label name is the same as the label string. Each Bar name is "barN". For xcpustate, the available resources are:
NOTESXcpustate is meant to be easy to port, and extend to monitor a wide variety of statistics.SEE ALSOxperfmon, xload, xmeterAUTHORSMark Moraes at D. E. Shaw wrote the original X code and the SGI IRIX code. He also enhanced the code for the Bar widget to support color. John DiMarco at the University of Toronto is the current maintainer. He contributed to the color support, fixed some minor problems, added support for SunOS 4.x multiprocessors, SunOS 5.x, disks, Omni network coprocessors, AIX (SMP on AIX 4.x) and RSTAT. Thanks to David O'Brien of the University of California, Davis for the 4.4BSD code, Chris Siebenmann of the University of Toronto for the code for 4.3BSD systems; Walter D. Poxon from Cray Research for the code for Cray machines running Unicos; Melinda Shore at mt Xinu for the code for Mach systems; Bill Kucharski at Solbourne for the code for Solbourne systems; Salvador Pinto Abreu at Universidade Nova de Lisboa, Portugal, for the code for Ultrix multiprocessors; Hugues Leroy at Irisa, Rennes, France for the code for Gould NP1 bi-processors, Bruce Frost at NCR for the code for (Dell) SVR4 and NCR systems, and Kumsup Lee at the University of Minnesota and Greg Nakhimovsky at Sun Microsystems for the Linux code. Thanks also to Robert Montjoy from the University of Cincinatti for contributing and testing some of the SunOS 5.x code, to Dave Cahlander from Cray for cleaning up the X resource code, and to Ron Wigmore from Ryerson Polytechnic University for his assistance with the AIX port.BUGSThe RSTAT RPC protocol supports only one processor and four disks on the remote system. On a multiprocessor, the CPU data reported by RSTAT will be an average of all the active CPUs on the machine.For some operating systems, there may be internal compile-time limits on the number of CPUs or disks supported. If there are compile-time limits, they are reported by the output of the -version flag. Xcpustate may initially display nonsensical data, before being updated the first time. The use of very small (significantly less than one second) intervals may result in xcpustate using significant resources, particularly when running over the network. A minimum interval may be specified as a compile-time option, and intervals less than this will not be permitted.
|