From 775af457c320f74e4035b2bcd9532a9ad7861733 Mon Sep 17 00:00:00 2001 From: Yuichi SATO Date: Sat, 20 Jul 2019 20:15:52 +0900 Subject: [PATCH] [JM:01533] sysstat-12.0.5 original and translation_list --- manual/sysstat/original/man1/cifsiostat.1 | 194 +++ manual/sysstat/original/man1/iostat.1 | 523 ++++++ manual/sysstat/original/man1/mpstat.1 | 307 ++++ manual/sysstat/original/man1/pidstat.1 | 673 ++++++++ manual/sysstat/original/man1/sadf.1 | 348 ++++ manual/sysstat/original/man1/sar.1 | 2427 ++++++++++++++++++++++++++++ manual/sysstat/original/man1/tapestat.1 | 263 +++ manual/sysstat/original/man5/sysstat.5 | 179 ++ manual/sysstat/original/man8/sa1.8 | 86 + manual/sysstat/original/man8/sa2.8 | 72 + manual/sysstat/original/man8/sadc.8 | 244 +++ manual/sysstat/original/sysstat-12.0.5.lsm | 35 + manual/sysstat/translation_list | 11 + 13 files changed, 5362 insertions(+) create mode 100644 manual/sysstat/original/man1/cifsiostat.1 create mode 100644 manual/sysstat/original/man1/iostat.1 create mode 100644 manual/sysstat/original/man1/mpstat.1 create mode 100644 manual/sysstat/original/man1/pidstat.1 create mode 100644 manual/sysstat/original/man1/sadf.1 create mode 100644 manual/sysstat/original/man1/sar.1 create mode 100644 manual/sysstat/original/man1/tapestat.1 create mode 100644 manual/sysstat/original/man5/sysstat.5 create mode 100644 manual/sysstat/original/man8/sa1.8 create mode 100644 manual/sysstat/original/man8/sa2.8 create mode 100644 manual/sysstat/original/man8/sadc.8 create mode 100644 manual/sysstat/original/sysstat-12.0.5.lsm create mode 100644 manual/sysstat/translation_list diff --git a/manual/sysstat/original/man1/cifsiostat.1 b/manual/sysstat/original/man1/cifsiostat.1 new file mode 100644 index 00000000..c012088d --- /dev/null +++ b/manual/sysstat/original/man1/cifsiostat.1 @@ -0,0 +1,194 @@ +.TH CIFSIOSTAT 1 "JULY 2018" Linux "Linux User's Manual" -*- nroff -*- +.SH NAME +cifsiostat \- Report CIFS statistics. +.SH SYNOPSIS +.ie 'yes'no' \{ +.B cifsiostat [ -h ] [ -k | -m ] [ -t ] [ -V ] [ --debuginfo ] [ --dec={ 0 | 1 | 2 } ] [ --human ] [ +.I interval +.B [ +.I count +.B ] ] +.\} +.el \{ +.B cifsiostat [ -h ] [ -k | -m ] [ -t ] [ -V ] [ --dec={ 0 | 1 | 2 } ] [ --human ] [ +.I interval +.B [ +.I count +.B ] ] +.\} +.SH DESCRIPTION +The +.B cifsiostat +command displays statistics about read and write operations +on CIFS filesystems. + +The +.I interval +parameter specifies the amount of time in seconds between +each report. The first report contains statistics for the time since +system startup (boot). Each subsequent report contains statistics +collected during the interval since the previous report. +A report consists of a CIFS header row followed by +a line of statistics for each CIFS filesystem that is mounted. +The +.I count +parameter can be specified in conjunction with the +.I interval +parameter. If the +.I count +parameter is specified, the value of +.I count +determines the number of reports generated at +.I interval +seconds apart. If the +.I interval +parameter is specified without the +.I count +parameter, the +.B cifsiostat +command generates reports continuously. + +.SH REPORT +The CIFS report provides statistics for each mounted CIFS filesystem. +The report shows the following fields: + +.B Filesystem: +.RS +This columns shows the mount point of the CIFS filesystem. + +.RE +.B rB/s (rkB/s, rMB/s) +.RS +Indicate the average number of bytes (kilobytes, megabytes) read per second. + +.RE +.B wB/s (wkB/s, wMB/s) +.RS +Indicate the average number of bytes (kilobytes, megabytes) written per second. + +.RE +.B rop/s +.RS +Indicate the number of 'read' operations that were issued to the filesystem +per second. + +.RE +.B wop/s +.RS +Indicate the number of 'write' operations that were issued to the filesystem +per second. + +.RE +.B fo/s +.RS +Indicate the number of open files per second. + +.RE +.B fc/s +.RS +Indicate the number of closed files per second. + +.RE +.B fd/s +.RS +Indicate the number of deleted files per second. +.RE +.RE +.SH OPTIONS +.if 'yes'no' \{ +.IP --debuginfo +Print debug output to stderr. +.\} +.IP "--dec={ 0 | 1 | 2 }" +Specify the number of decimal places to use (0 to 2, default value is 2). +.IP -h +Make the CIFS report easier to read by a human. +.B --human +is enabled implicitly with this option. +.IP --human +Print sizes in human readable format (e.g. 1.0k, 1.2M, etc.) +The units displayed with this option supersede any other default units (e.g. +kilobytes, sectors...) associated with the metrics. +.IP -k +Display statistics in kilobytes per second. +.IP -m +Display statistics in megabytes per second. +.IP -t +Print the time for each report displayed. The timestamp format may depend +on the value of the S_TIME_FORMAT environment variable (see below). +.IP -V +Print version number then exit. + +.SH ENVIRONMENT +The +.B cifsiostat +command takes into account the following environment variables: + +.IP S_COLORS +When this variable is set, display statistics in color on the terminal. +Possible values for this variable are +.IR never , +.IR always +or +.IR auto +(the latter is the default). + +Please note that the color (being red, yellow, or some other color) used to display a value +is not indicative of any kind of issue simply because of the color. It only indicates different +ranges of values. + +.IP S_COLORS_SGR +Specify the colors and other attributes used to display statistics on the terminal. +Its value is a colon-separated list of capabilities that defaults to +.BR I=32;22:N=34;1:Z=34;22 . +Supported capabilities are: + +.RS +.TP +.B I= +SGR substring for filesystem names. + +.TP +.B N= +SGR substring for non-zero statistics values. + +.TP +.B Z= +SGR substring for zero values. +.RE + +.IP S_TIME_FORMAT +If this variable exists and its value is +.BR ISO +then the current locale will be ignored when printing the date in the report +header. The +.B cifsiostat +command will use the ISO 8601 format (YYYY-MM-DD) instead. +The timestamp displayed with option -t will also be compliant with ISO 8601 +format. + +.SH BUG +.I /proc +filesystem must be mounted for +.B cifsiostat +to work. + +.SH FILE +.I /proc/fs/cifs/Stats +contains CIFS statistics. +.SH AUTHORS +Written by Ivana Varekova (varekova redhat.com) + +Maintained by Sebastien Godard (sysstat orange.fr) +.SH SEE ALSO +.BR sar (1), +.BR pidstat (1), +.BR mpstat (1), +.BR vmstat (8), +.BR iostat (1), +.BR tapestat (1), +.BR nfsiostat (1) + +.I https://github.com/sysstat/sysstat + +.I http://pagesperso-orange.fr/sebastien.godard/ diff --git a/manual/sysstat/original/man1/iostat.1 b/manual/sysstat/original/man1/iostat.1 new file mode 100644 index 00000000..f1db4c80 --- /dev/null +++ b/manual/sysstat/original/man1/iostat.1 @@ -0,0 +1,523 @@ +.TH IOSTAT 1 "JULY 2018" Linux "Linux User's Manual" -*- nroff -*- +.SH NAME +iostat \- Report Central Processing Unit (CPU) statistics and input/output +statistics for devices and partitions. +.SH SYNOPSIS +.ie 'yes'no' \{ +.B iostat [ -c ] [ -d ] [ -h ] [ -k | -m ] [ -N ] [ -s ] [ -t ] [ -V ] [ -x ] [ -y ] [ -z ] +.B [ --dec={ 0 | 1 | 2 } ] [ -j { ID | LABEL | PATH | UUID | ... } ] [ -o JSON ] +.B [ [ -H ] -g +.I group_name +.B ] [ --human ] [ -p [ +.I device +.B [,...] | ALL ] ] [ +.I device +.B [...] | ALL ] [ --debuginfo ] [ +.I interval +.B [ +.I count +.B ] ] +.\} +.el \{ +.B iostat [ -c ] [ -d ] [ -h ] [ -k | -m ] [ -N ] [ -s ] [ -t ] [ -V ] [ -x ] [ -y ] [ -z ] +.B [ --dec={ 0 | 1 | 2 } ] [ -j { ID | LABEL | PATH | UUID | ... } ] [ -o JSON ] +.B [ [ -H ] -g +.I group_name +.B ] [ --human ] [ -p [ +.I device +.B [,...] | ALL ] ] [ +.I device +.B [...] | ALL ] [ +.I interval +.B [ +.I count +.B ] ] +.\} +.SH DESCRIPTION +The +.B iostat +command is used for monitoring system input/output device +loading by observing the time the devices are active in relation +to their average transfer rates. The +.B iostat +command generates reports +that can be used to change system configuration to better balance +the input/output load between physical disks. + +The first report generated by the +.B iostat +command provides statistics +concerning the time since the system was booted, unless the +.B -y +option is used (in this case, this first report is omitted). +Each subsequent report +covers the time since the previous report. All statistics are reported +each time the +.B iostat +command is run. The report consists of a +CPU header row followed by a row of +CPU statistics. On +multiprocessor systems, CPU statistics are calculated system-wide +as averages among all processors. A device header row is displayed +followed by a line of statistics for each device that is configured. + +The +.I interval +parameter specifies the amount of time in seconds between +each report. The +.I count +parameter can be specified in conjunction with the +.I interval +parameter. If the +.I count +parameter is specified, the value of +.I count +determines the number of reports generated at +.I interval +seconds apart. If the +.I interval +parameter is specified without the +.I count +parameter, the +.B iostat +command generates reports continuously. + +.SH REPORTS +The +.B iostat +command generates two types of reports, the CPU +Utilization report and the Device Utilization report. +.IP "CPU Utilization Report" +The first report generated by the +.B iostat +command is the CPU +Utilization Report. For multiprocessor systems, the CPU values are +global averages among all processors. +The report has the following format: + +.B %user +.RS +.RS +Show the percentage of CPU utilization that occurred while +executing at the user level (application). +.RE + +.B %nice +.RS +Show the percentage of CPU utilization that occurred while +executing at the user level with nice priority. +.RE + +.B %system +.RS +Show the percentage of CPU utilization that occurred while +executing at the system level (kernel). +.RE + +.B %iowait +.RS +Show the percentage of time that the CPU or CPUs were idle during which +the system had an outstanding disk I/O request. +.RE + +.B %steal +.RS +Show the percentage of time spent in involuntary wait by the virtual CPU +or CPUs while the hypervisor was servicing another virtual processor. +.RE + +.B %idle +.RS +Show the percentage of time that the CPU or CPUs were idle and the system +did not have an outstanding disk I/O request. +.RE +.RE +.IP "Device Utilization Report" +The second report generated by the +.B iostat +command is the Device Utilization +Report. The device report provides statistics on a per physical device +or partition basis. Block devices and partitions for which statistics are +to be displayed may be entered on the command line. +If no device nor partition +is entered, then statistics are displayed +for every device used by the system, and +providing that the kernel maintains statistics for it. +If the +.B ALL +keyword is given on the command line, then statistics are +displayed for every device defined by the system, including those +that have never been used. +Transfer rates are shown in 1K blocks by default, unless the environment +variable POSIXLY_CORRECT is set, in which case 512-byte blocks are used. +The report may show the following fields, +depending on the flags used: + +.B Device: +.RS +.RS +This column gives the device (or partition) name as listed in the /dev +directory. + +.RE +.B tps +.RS +Indicate the number of transfers per second that were issued +to the device. A transfer is an I/O request to the +device. Multiple logical requests can be combined into a single I/O +request to the device. A transfer is of indeterminate size. + +.RE +.B Blk_read/s (kB_read/s, MB_read/s) +.RS +Indicate the amount of data read from the device expressed in a number of +blocks (kilobytes, megabytes) per second. Blocks are equivalent to sectors +and therefore have a size of 512 bytes. + +.RE +.B Blk_wrtn/s (kB_wrtn/s, MB_wrtn/s) +.RS +Indicate the amount of data written to the device expressed in a number of +blocks (kilobytes, megabytes) per second. + +.RE +.B Blk_read (kB_read, MB_read) +.RS +The total number of blocks (kilobytes, megabytes) read. + +.RE +.B Blk_wrtn (kB_wrtn, MB_wrtn) +.RS +The total number of blocks (kilobytes, megabytes) written. + +.RE +.B r/s +.RS +The number (after merges) of read requests completed per second for the device. + +.RE +.B w/s +.RS +The number (after merges) of write requests completed per second for the device. + +.RE +.B sec/s (kB/s, MB/s) +.RS +The number of sectors (kilobytes, megabytes) read from or written to the device +per second. + +.RE +.B rsec/s (rkB/s, rMB/s) +.RS +The number of sectors (kilobytes, megabytes) read from the device per second. + +.RE +.B wsec/s (wkB/s, wMB/s) +.RS +The number of sectors (kilobytes, megabytes) written to the device per second. + +.RE +.B rqm/s +.RS +The number of I/O requests merged per second that were queued to the device. + +.RE +.B rrqm/s +.RS +The number of read requests merged per second that were queued to the device. + +.RE +.B wrqm/s +.RS +The number of write requests merged per second that were queued to the device. + +.RE +.B %rrqm +.RS +The percentage of read requests merged together before being sent to the device. + +.RE +.B %wrqm +.RS +The percentage of write requests merged together before being sent to the device. + +.RE +.B areq-sz +.RS +The average size (in kilobytes) of the I/O requests that were issued to the device. +.br +Note: In previous versions, this field was known as avgrq-sz and was expressed in +sectors. + +.RE +.B rareq-sz +.RS +The average size (in kilobytes) of the read requests that were issued to the +device. + +.RE +.B wareq-sz +.RS +The average size (in kilobytes) of the write requests that were issued to the +device. + +.RE +.B await +.RS +The average time (in milliseconds) for I/O requests issued to the device +to be served. This includes the time spent by the requests in queue and +the time spent servicing them. + +.RE +.B r_await +.RS +The average time (in milliseconds) for read requests issued to the device +to be served. This includes the time spent by the requests in queue and +the time spent servicing them. + +.RE +.B w_await +.RS +The average time (in milliseconds) for write requests issued to the device +to be served. This includes the time spent by the requests in queue and +the time spent servicing them. + +.RE +.B aqu-sz +.RS +The average queue length of the requests that were issued to the device. +.br +Note: In previous versions, this field was known as avgqu-sz. + +.RE +.B svctm +.RS +The average service time (in milliseconds) for I/O requests that were issued +to the device. Warning! Do not trust this field any more. +This field will be removed in a future sysstat version. + +.RE +.B %util +.RS +Percentage of elapsed time during which I/O requests were issued to the device +(bandwidth utilization for the device). Device saturation occurs when this +value is close to 100% for devices serving requests serially. +But for devices serving requests in parallel, such as RAID arrays and +modern SSDs, this number does not reflect their performance limits. +.RE +.RE +.SH OPTIONS +.IP -c +Display the CPU utilization report. +.IP -d +Display the device utilization report. +.if 'yes'no' \{ +.IP --debuginfo +Print debug output to stderr. +.\} +.IP "--dec={ 0 | 1 | 2 }" +Specify the number of decimal places to use (0 to 2, default value is 2). +.IP "-g group_name { device [...] | ALL } +Display statistics for a group of devices. +The +.B iostat +command reports statistics for each individual device in the list +then a line of global statistics for the group displayed as +.B group_name +and made up of all the devices in the list. The +.B ALL +keyword means that all the block devices defined by the system shall be +included in the group. +.IP -H +This option must be used with option -g and indicates that only global +statistics for the group are to be displayed, and not statistics for +individual devices in the group. +.IP -h +Make the Device Utilization Report easier to read by a human. +.B --human +is enabled implicitly with this option. +.IP --human +Print sizes in human readable format (e.g. 1.0k, 1.2M, etc.) +The units displayed with this option supersede any other default units (e.g. +kilobytes, sectors...) associated with the metrics. +.IP "-j { ID | LABEL | PATH | UUID | ... } [ device [...] | ALL ]" +Display persistent device names. Options +.BR ID , +.BR LABEL , +etc. specify the type of the persistent name. These options are not limited, +only prerequisite is that directory with required persistent names is present in +.IR /dev/disk . +Optionally, multiple devices can be specified in the chosen persistent name type. +Because persistent device names are usually long, option +.IP -k +Display statistics in kilobytes per second. +.IP -m +Display statistics in megabytes per second. +.IP -N +Display the registered device mapper names for any device mapper devices. +Useful for viewing LVM2 statistics. +.IP "-o JSON" +Display the statistics in JSON (Javascript Object Notation) format. +JSON output field order is undefined, and new fields may be added +in the future. +.IP "-p [ { device [,...] | ALL } ]" +The -p option displays statistics for +block devices and all their partitions that are used by the system. +If a device name is entered on the command line, then statistics for it +and all its partitions are displayed. Last, the +.B ALL +keyword indicates that statistics have to be displayed for all the block +devices and partitions defined by the system, including those that have +never been used. If option +.B -j +is defined before this option, devices entered on the command line can be +specified with the chosen persistent name type. +.IP -s +Display a short (narrow) version of the report that should fit in 80 +characters wide screens. +.IP -t +Print the time for each report displayed. The timestamp format may depend +on the value of the S_TIME_FORMAT environment variable (see below). +.IP -V +Print version number then exit. +.IP -x +Display extended statistics. +.IP -y +Omit first report with statistics since system boot, if displaying +multiple records at given interval. +.IP -z +Tell +.B iostat +to omit output for any devices for which there was no activity +during the sample period. + +.SH ENVIRONMENT +The +.B iostat +command takes into account the following environment variables: + +.IP POSIXLY_CORRECT +When this variable is set, transfer rates are shown in 512-byte blocks instead +of the default 1K blocks. + +.IP S_COLORS +When this variable is set, display statistics in color on the terminal. +Possible values for this variable are +.IR never , +.IR always +or +.IR auto +(the latter is the default). + +Please note that the color (being red, yellow, or some other color) used to display a value +is not indicative of any kind of issue simply because of the color. It only indicates different +ranges of values. + +.IP S_COLORS_SGR +Specify the colors and other attributes used to display statistics on the terminal. +Its value is a colon-separated list of capabilities that defaults to +.BR H=31;1:I=32;22:M=35;1:N=34;1:Z=34;22 . +Supported capabilities are: + +.RS +.TP +.B H= +SGR (Select Graphic Rendition) substring for percentage values greater than or equal to 75%. + +.TP +.B I= +SGR substring for device names. + +.TP +.B M= +SGR substring for percentage values in the range from 50% to 75%. + +.TP +.B N= +SGR substring for non-zero statistics values. + +.TP +.B Z= +SGR substring for zero values. +.RE + +.IP S_TIME_FORMAT +If this variable exists and its value is +.BR ISO +then the current locale will be ignored when printing the date in the report +header. The +.B iostat +command will use the ISO 8601 format (YYYY-MM-DD) instead. +The timestamp displayed with option -t will also be compliant with ISO 8601 +format. + +.SH EXAMPLES +.B iostat +.RS +Display a single history since boot report for all CPU and Devices. + +.RE +.B iostat -d 2 +.RS +Display a continuous device report at two second intervals. + +.RE +.B iostat -d 2 6 +.RS +Display six reports at two second intervals for all devices. + +.RE +.B iostat -x sda sdb 2 6 +.RS +Display six reports of extended statistics at two second intervals for devices +sda and sdb. + +.RE +.B iostat -p sda 2 6 +.RS +Display six reports at two second intervals for device sda and all its +partitions (sda1, etc.) +.SH BUGS +.I /proc +filesystem must be mounted for +.B iostat +to work. + +Kernels older than 2.6.x are no longer supported. + +The average service time (svctm field) value is meaningless, +as I/O statistics are now calculated at block level, and we don't know +when the disk driver starts to process a request. For this reason, +this field will be removed in a future sysstat version. +.SH FILES +.I /proc/stat +contains system statistics. + +.I /proc/uptime +contains system uptime. + +.I /proc/diskstats +contains disks statistics. + +.I /sys +contains statistics for block devices. + +.I /proc/self/mountstats +contains statistics for network filesystems. + +.I /dev/disk +contains persistent device names. +.SH AUTHOR +Sebastien Godard (sysstat orange.fr) +.SH SEE ALSO +.BR sar (1), +.BR pidstat (1), +.BR mpstat (1), +.BR vmstat (8), +.BR tapestat (1), +.BR nfsiostat (1), +.BR cifsiostat (1) + +.I https://github.com/sysstat/sysstat + +.I http://pagesperso-orange.fr/sebastien.godard/ diff --git a/manual/sysstat/original/man1/mpstat.1 b/manual/sysstat/original/man1/mpstat.1 new file mode 100644 index 00000000..ab34787c --- /dev/null +++ b/manual/sysstat/original/man1/mpstat.1 @@ -0,0 +1,307 @@ +.TH MPSTAT 1 "JULY 2018" Linux "Linux User's Manual" -*- nroff -*- +.SH NAME +mpstat \- Report processors related statistics. +.SH SYNOPSIS +.B mpstat [ -A ] [ --dec={ 0 | 1 | 2 } ] [ -n ] [ -u ] [ -V ] [ -I { +.I keyword +.B [,...] | ALL } ] [ -N { +.I node_list +.B | ALL } ] [ -o JSON ] [ -P { +.I cpu_list +.B | ALL } ] [ +.I interval +.B [ +.I count +.B ] ] +.SH DESCRIPTION +The +.B mpstat +command writes to standard output activities for each available processor, +processor 0 being the first one. +Global average activities among all processors are also reported. +The +.B mpstat +command can be used both on SMP and UP machines, but in the latter, only global +average activities will be printed. If no activity has been selected, then the +default report is the CPU utilization report. + +The +.I interval +parameter specifies the amount of time in seconds between each report. +A value of 0 (or no parameters at all) indicates that processors statistics are +to be reported for the time since system startup (boot). +The +.I count +parameter can be specified in conjunction with the +.I interval +parameter if this one is not set to zero. The value of +.I count +determines the number of reports generated at +.I interval +seconds apart. If the +.I interval +parameter is specified without the +.I count +parameter, the +.B mpstat +command generates reports continuously. + +.SH OPTIONS +.IP -A +This option is equivalent to specifying +.BR "-n -u -I ALL -N ALL -P ALL" +.IP "--dec={ 0 | 1 | 2 }" +Specify the number of decimal places to use (0 to 2, default value is 2). +.IP "-I { keyword [,...] | ALL }" +Report interrupts statistics. + +Possible keywords are +.BR CPU , +.BR SCPU , +and +.BR SUM . + +With the +.B CPU +keyword, the number of each individual interrupt received per +second by the CPU or CPUs is displayed. Interrupts are those listed +in /proc/interrupts file. + +With the +.B SCPU +keyword, the number of each individual software interrupt received per +second by the CPU or CPUs is displayed. This option works only +with kernels 2.6.31 and later. Software interrupts are those listed +in /proc/softirqs file. + +With the +.B SUM +keyword, the +.B mpstat +command reports the total number of interrupts per processor. +The following values are displayed: + +.B CPU +.RS +.RS +Processor number. The keyword +.I all +indicates that statistics are calculated as averages among all +processors. +.RE + +.B intr/s +.RS +Show the total number of interrupts received per second by +the CPU or CPUs. +.RE + +The +.B ALL +keyword is equivalent to specifying all the keywords above and +therefore all the interrupts statistics are displayed. +.RE +.RE +.IP "-N { node_list | ALL }" +Indicate the NUMA nodes for which statistics are to be reported. +.I node_list +is a list of comma-separated values or range of values (e.g., +.BR 0,2,4-7,12- ). +Note that node +.B all +is the global average among all nodes. The +.B ALL +keyword indicates that statistics are to be reported for all nodes. +.IP -n +Report summary CPU statistics based on NUMA node placement. The following +values are displayed: + +.B NODE +.RS +.RS +Node number. The keyword +.I all +indicates that statistics are calculated as averages among all nodes. +.RE + +All the other fields are the same as those displayed with option -u +(see below). +.RE +.IP "-o JSON" +Display the statistics in JSON (Javascript Object Notation) format. +JSON output field order is undefined, and new fields may be added +in the future. +.IP "-P { cpu_list | ALL }" +Indicate the processors for which statistics are to be reported. +.I cpu_list +is a list of comma-separated values or range of values (e.g., +.BR 0,2,4-7,12- ). +Note that processor 0 is the first processor, and processor +.B all +is the global average among all processors. +The +.B ALL +keyword indicates that statistics are to be reported for all processors. +Offline processors are not displayed. +.IP -u +Report CPU utilization. The following values are displayed: + +.B CPU +.RS +.RS +Processor number. The keyword +.I all +indicates that statistics are calculated as averages among all +processors. +.RE + +.B %usr +.RS +Show the percentage of CPU utilization that occurred while +executing at the user level (application). +.RE + +.B %nice +.RS +Show the percentage of CPU utilization that occurred while +executing at the user level with nice priority. +.RE + +.B %sys +.RS +Show the percentage of CPU utilization that occurred while +executing at the system level (kernel). Note that this does not +include time spent servicing hardware and software interrupts. +.RE + +.B %iowait +.RS +Show the percentage of time that the CPU or CPUs were idle during which +the system had an outstanding disk I/O request. +.RE + +.B %irq +.RS +Show the percentage of time spent by the CPU or CPUs to service hardware +interrupts. +.RE + +.B %soft +.RS +Show the percentage of time spent by the CPU or CPUs to service software +interrupts. +.RE + +.B %steal +.RS +Show the percentage of time spent in involuntary wait by the virtual CPU +or CPUs while the hypervisor was servicing another virtual processor. +.RE + +.B %guest +.RS +Show the percentage of time spent by the CPU or CPUs to run a virtual +processor. +.RE + +.B %gnice +.RS +Show the percentage of time spent by the CPU or CPUs to run a niced +guest. +.RE + +.B %idle +.RS +Show the percentage of time that the CPU or CPUs were idle and the system +did not have an outstanding disk I/O request. +.RE +.RE +.IP -V +Print version number then exit. + +.SH ENVIRONMENT +The +.B mpstat +command takes into account the following environment variable: + +.IP S_COLORS +When this variable is set, display statistics in color on the terminal. +Possible values for this variable are +.IR never , +.IR always +or +.IR auto +(the latter is the default). + +Please note that the color (being red, yellow, or some other color) used to display a value +is not indicative of any kind of issue simply because of the color. It only indicates different +ranges of values. + +.IP S_COLORS_SGR +Specify the colors and other attributes used to display statistics on the terminal. +Its value is a colon-separated list of capabilities that defaults to +.BR H=31;1:I=32;22:M=35;1:N=34;1:Z=34;22 . +Supported capabilities are: + +.RS +.TP +.B H= +SGR (Select Graphic Rendition) substring for percentage values greater than or equal to 75%. + +.TP +.B I= +SGR substring for CPU number. + +.TP +.B M= +SGR substring for percentage values in the range from 50% to 75%. + +.TP +.B N= +SGR substring for non-zero statistics values. + +.TP +.B Z= +SGR substring for zero values. +.RE + +.IP S_TIME_FORMAT +If this variable exists and its value is +.BR ISO +then the current locale will be ignored when printing the date in the report header. +The +.B mpstat +command will use the ISO 8601 format (YYYY-MM-DD) instead. +The timestamp will also be compliant with ISO 8601 format. + +.SH EXAMPLES +.B mpstat 2 5 +.RS +Display five reports of global statistics among all processors at two second intervals. +.RE + +.B mpstat -P ALL 2 5 +.RS +Display five reports of statistics for all processors at two second intervals. + +.SH BUGS +.I /proc +filesystem must be mounted for the +.B mpstat +command to work. + +.SH FILES +.IR /proc +contains various files with system statistics. + +.SH AUTHOR +Sebastien Godard (sysstat orange.fr) +.SH SEE ALSO +.BR sar (1), +.BR pidstat (1), +.BR iostat (1), +.BR vmstat (8) + +.I https://github.com/sysstat/sysstat + +.I http://pagesperso-orange.fr/sebastien.godard/ diff --git a/manual/sysstat/original/man1/pidstat.1 b/manual/sysstat/original/man1/pidstat.1 new file mode 100644 index 00000000..20c8c9a4 --- /dev/null +++ b/manual/sysstat/original/man1/pidstat.1 @@ -0,0 +1,673 @@ +.TH PIDSTAT 1 "JULY 2018" Linux "Linux User's Manual" -*- nroff -*- +.SH NAME +pidstat \- Report statistics for Linux tasks. +.SH SYNOPSIS +.B pidstat [ -d ] [ -H ] [ -h ] [ -I ] [ -l ] [ -R ] [ -r ] [ -s ] [ -t ] [ -U [ +.I username +.B ] ] [ -u ] [ -V ] [ -v ] +.B [ -w ] [ -C +.I comm +.B ] [ -G +.I process_name +.B ] [ --dec={ 0 | 1 | 2 } ] [ --human ] [ -p { +.I pid +.B [,...] | SELF | ALL } ] [ -T { TASK | CHILD | ALL } ] [ +.I interval +.B [ +.I count +.B ] ] [ -e +.I program +.I args +.B ] +.SH DESCRIPTION +The +.B pidstat +command is used for monitoring individual tasks currently being managed +by the Linux kernel. +It writes to standard output activities for every task selected with option +.B -p +or for every task managed by the Linux kernel if option +.B -p ALL +has been used. Not selecting any tasks is equivalent to specifying +.B -p ALL +but only active tasks (tasks with non-zero statistics values) +will appear in the report. + +The +.B pidstat +command can also be used for monitoring the child processes of selected tasks. +Read about option +.B -T +below. + +The +.I interval +parameter specifies the amount of time in seconds between each report. +A value of 0 (or no parameters at all) indicates that tasks statistics are +to be reported for the time since system startup (boot). +The +.I count +parameter can be specified in conjunction with the +.I interval +parameter if this one is not set to zero. The value of +.I count +determines the number of reports generated at +.I interval +seconds apart. If the +.I interval +parameter is specified without the +.I count +parameter, the +.B pidstat +command generates reports continuously. + +You can select information about specific task activities using flags. +Not specifying any flags selects only CPU activity. + +.SH OPTIONS +.IP "-C comm" +Display only tasks whose command name includes the string +.IR comm . +This string can be a regular expression. +.IP -d +Report I/O statistics (kernels 2.6.20 and later only). +The following values may be displayed: + +.B UID +.RS +.RS +The real user identification number of the task being monitored. +.RE + +.B USER +.RS +The name of the real user owning the task being monitored. +.RE + +.B PID +.RS +The identification number of the task being monitored. +.RE + +.B kB_rd/s +.RS +Number of kilobytes the task has caused to be read from disk +per second. +.RE + +.B kB_wr/s +.RS +Number of kilobytes the task has caused, or shall cause to be +written to disk per second. +.RE + +.B kB_ccwr/s +.RS +Number of kilobytes whose writing to disk has been cancelled by +the task. This may occur when the task truncates some +dirty pagecache. In this case, some IO which another task has +been accounted for will not be happening. +.RE + +.B iodelay +.RS +Block I/O delay of the task being monitored, +measured in clock ticks. This metric includes the delays spent +waiting for sync block I/O completion and for swapin block I/O +completion. +.RE + +.B Command +.RS +The command name of the task. +.RE +.RE +.IP "--dec={ 0 | 1 | 2 }" +Specify the number of decimal places to use (0 to 2, default value is 2). +.IP "-e program args" +Execute +.IR program +with given arguments +.IR args +and monitor it with +.B pidstat. +.B pidstat +stops when +.IR program +terminates. +.IP "-G process_name" +Display only processes whose command name includes the string +.IR process_name . +This string can be a regular expression. If option -t is used +together with option -G then the threads belonging to that +process are also displayed (even if their command name doesn't +include the string +.IR process_name ). +.IP -H +Display timestamp in seconds since the epoch. +.IP -h +Display all activities horizontally on a single line, with no +average statistics at the end of the report. This is +intended to make it easier to be parsed by other programs. +.IP --human +Print sizes in human readable format (e.g. 1.0k, 1.2M, etc.) +The units displayed with this option supersede any other default units (e.g. +kilobytes, sectors...) associated with the metrics. +.IP -I +In an SMP environment, indicate that tasks CPU usage +(as displayed by option +.B -u +) should be divided by the total number of processors. +.IP -l +Display the process command name and all its arguments. +.IP "-p { pid [,...] | SELF | ALL }" +Select tasks (processes) for which statistics are to be reported. +.I pid +is the process identification number. The +.B SELF +keyword indicates that statistics are to be reported for the +.B pidstat +process itself, whereas the +.B ALL +keyword indicates that statistics are to be reported for all the +tasks managed by the system. +.IP -R +Report realtime priority and scheduling policy information. +The following values may be displayed: + +.B UID +.RS +.RS +The real user identification number of the task being monitored. +.RE + +.B USER +.RS +The name of the real user owning the task being monitored. +.RE + +.B PID +.RS +The identification number of the task being monitored. +.RE + +.B prio +.RS +The realtime priority of the task being monitored. +.RE + +.B policy +.RS +The scheduling policy of the task being monitored. +.RE + +.B Command +.RS +The command name of the task. +.RE +.RE +.IP -r +Report page faults and memory utilization. + +When reporting statistics for individual tasks, +the following values may be displayed: + +.B UID +.RS +.RS +The real user identification number of the task being monitored. +.RE + +.B USER +.RS +The name of the real user owning the task being monitored. +.RE + +.B PID +.RS +The identification number of the task being monitored. +.RE + +.B minflt/s +.RS +Total number of minor faults the task has made per second, those +which have not required loading a memory page from disk. +.RE + +.B majflt/s +.RS +Total number of major faults the task has made per second, those +which have required loading a memory page from disk. +.RE + +.B VSZ +.RS +Virtual Size: The virtual memory usage of entire task in kilobytes. +.RE + +.B RSS +.RS +Resident Set Size: The non-swapped physical memory +used by the task in kilobytes. +.RE + +.B %MEM +.RS +The tasks's currently used share of available physical memory. +.RE + +.B Command +.RS +The command name of the task. +.RE + +When reporting global statistics for tasks and all their children, +the following values may be displayed: + +.B UID +.RS +The real user identification number of the task which is being monitored +together with its children. +.RE + +.B USER +.RS +The name of the real user owning the task which is being monitored +together with its children. +.RE + +.B PID +.RS +The identification number of the task which is being monitored +together with its children. +.RE + +.B minflt-nr +.RS +Total number of minor faults made by the task and all its children, +and collected during the interval of time. +.RE + +.B majflt-nr +.RS +Total number of major faults made by the task and all its children, +and collected during the interval of time. +.RE + +.B Command +.RS +The command name of the task which is being monitored +together with its children. +.RE +.RE +.IP -s +Report stack utilization. +The following values may be displayed: + +.B UID +.RS +.RS +The real user identification number of the task being monitored. +.RE + +.B USER +.RS +The name of the real user owning the task being monitored. +.RE + +.B PID +.RS +The identification number of the task being monitored. +.RE + +.B StkSize +.RS +The amount of memory in kilobytes reserved for the task as stack, +but not necessarily used. +.RE + +.B StkRef +.RS +The amount of memory in kilobytes used as stack, referenced by the task. +.RE + +.B Command +.RS +The command name of the task. +.RE +.RE +.IP "-T { TASK | CHILD | ALL }" +This option specifies what has to be monitored by the +.B pidstat +command. The +.B TASK +keyword indicates that statistics are to be reported for individual tasks +(this is the default option) whereas the +.B CHILD +keyword indicates that statistics are to be globally reported for the +selected tasks and all their children. The +.B ALL +keyword indicates that statistics are to be reported for +individual tasks and globally for the selected +tasks and their children. + +Note: Global statistics for tasks and all their children are not available +for all options of +.B pidstat. +Also these statistics are not necessarily relevant to current time interval: +The statistics of a child process are collected only when it finishes or +it is killed. +.IP -t +Also display statistics for threads associated with selected tasks. + +This option adds the following values to the reports: + +.B TGID +.RS +.RS +The identification number of the thread group leader. +.RE + +.B TID +.RS +The identification number of the thread being monitored. +.RE +.RE +.IP "-U [ username ]" +Display the real user name of the tasks being monitored instead of the UID. +If +.I username +is specified, then only tasks belonging to the specified user are displayed. +.IP -u +Report CPU utilization. + +When reporting statistics for individual tasks, +the following values may be displayed: + +.B UID +.RS +.RS +The real user identification number of the task being monitored. +.RE + +.B USER +.RS +The name of the real user owning the task being monitored. +.RE + +.B PID +.RS +The identification number of the task being monitored. +.RE + +.B %usr +.RS +Percentage of CPU used by the task while executing at the user level +(application), with or without nice priority. Note that this field +does NOT include time spent running a virtual processor. +.RE + +.B %system +.RS +Percentage of CPU used by the task while executing at the system level +(kernel). +.RE + +.B %guest +.RS +Percentage of CPU spent by the task in virtual machine (running a virtual +processor). +.RE + +.B %wait +.RS +Percentage of CPU spent by the task while waiting to run. +.RE + +.B %CPU +.RS +Total percentage of CPU time used by the task. In an SMP environment, +the task's CPU usage will be divided by the total number of CPU's if +option +.B -I +has been entered on the command line. +.RE + +.B CPU +.RS +Processor number to which the task is attached. +.RE + +.B Command +.RS +The command name of the task. +.RE + +When reporting global statistics for tasks and all their children, +the following values may be displayed: + +.B UID +.RS +The real user identification number of the task which is being monitored +together with its children. +.RE + +.B USER +.RS +The name of the real user owning the task which is being monitored +together with its children. +.RE + +.B PID +.RS +The identification number of the task which is being monitored +together with its children. +.RE + +.B usr-ms +.RS +Total number of milliseconds spent +by the task and all its children while executing at the +user level (application), with or without nice priority, and +collected during the interval of time. Note that this field does +NOT include time spent running a virtual processor. +.RE + +.B system-ms +.RS +Total number of milliseconds spent +by the task and all its children while executing at the +system level (kernel), and collected during the interval of time. +.RE + +.B guest-ms +.RS +Total number of milliseconds spent +by the task and all its children in virtual machine (running a virtual +processor). +.RE + +.B Command +.RS +The command name of the task which is being monitored +together with its children. +.RE +.RE +.IP -V +Print version number then exit. +.IP -v +Report values of some kernel tables. The following values may be displayed: + +.B UID +.RS +.RS +The real user identification number of the task being monitored. +.RE + +.B USER +.RS +The name of the real user owning the task being monitored. +.RE + +.B PID +.RS +The identification number of the task being monitored. +.RE + +.B threads +.RS +Number of threads associated with current task. +.RE + +.B fd-nr +.RS +Number of file descriptors associated with current task. +.RE + +.B Command +.RS +The command name of the task. +.RE +.RE +.IP -w +Report task switching activity (kernels 2.6.23 and later only). +The following values may be displayed: + +.B UID +.RS +.RS +The real user identification number of the task being monitored. +.RE + +.B USER +.RS +The name of the real user owning the task being monitored. +.RE + +.B PID +.RS +The identification number of the task being monitored. +.RE + +.B cswch/s +.RS +Total number of voluntary context switches the task made per second. +A voluntary context switch occurs when a task blocks because it +requires a resource that is unavailable. +.RE + +.B nvcswch/s +.RS +Total number of non voluntary context switches the task made per second. +A involuntary context switch takes place when a task executes +for the duration of its time slice and then is forced to relinquish the +processor. +.RE + +.B Command +.RS +The command name of the task. +.RE +.RE +.SH ENVIRONMENT +The +.B pidstat +command takes into account the following environment variables: + +.IP S_COLORS +When this variable is set, display statistics in color on the terminal. +Possible values for this variable are +.IR never , +.IR always +or +.IR auto +(the latter is the default). + +Please note that the color (being red, yellow, or some other color) used to display a value +is not indicative of any kind of issue simply because of the color. It only indicates different +ranges of values. + +.IP S_COLORS_SGR +Specify the colors and other attributes used to display statistics on the terminal. +Its value is a colon-separated list of capabilities that defaults to +.BR H=31;1:I=32;22:M=35;1:N=34;1:Z=34;22 . +Supported capabilities are: + +.RS +.TP +.B H= +SGR (Select Graphic Rendition) substring for percentage values greater than or equal to 75%. + +.TP +.B I= +SGR substring for item values like PID, UID or CPU number. + +.TP +.B M= +SGR substring for percentage values in the range from 50% to 75%. + +.TP +.B N= +SGR substring for non-zero statistics values and for tasks names. + +.TP +.B Z= +SGR substring for zero values and for threads names. +.RE + +.IP S_TIME_FORMAT +If this variable exists and its value is +.BR ISO +then the current locale will be ignored when printing the date in the report header. +The +.B pidstat +command will use the ISO 8601 format (YYYY-MM-DD) instead. +The timestamp will also be compliant with ISO 8601 format. + +.SH EXAMPLES +.B pidstat 2 5 +.RS +Display five reports of CPU statistics for every active task in the system +at two second intervals. +.RE + +.B pidstat -r -p 1643 2 5 +.RS +Display five reports of page faults and memory statistics for +PID 1643 at two second intervals. +.RE + +.B pidstat -C """fox|bird"" -r -p ALL +.RS +Display global page faults and memory statistics for all the +processes whose command name includes the string "fox" or "bird". +.RE + +.B pidstat -T CHILD -r 2 5 +.RS +Display five reports of page faults statistics at two second intervals +for the child processes of all tasks in the system. Only child processes +with non-zero statistics values are displayed. +.SH BUGS +.I /proc +filesystem must be mounted for the +.B pidstat +command to work. + +.SH FILES +.IR /proc +contains various files with system statistics. + +.SH AUTHOR +Sebastien Godard (sysstat orange.fr) +.SH SEE ALSO +.BR sar (1), +.BR top (1), +.BR ps (1), +.BR mpstat (1), +.BR iostat (1), +.BR vmstat (8) + +.I https://github.com/sysstat/sysstat + +.I http://pagesperso-orange.fr/sebastien.godard/ diff --git a/manual/sysstat/original/man1/sadf.1 b/manual/sysstat/original/man1/sadf.1 new file mode 100644 index 00000000..047006cd --- /dev/null +++ b/manual/sysstat/original/man1/sadf.1 @@ -0,0 +1,348 @@ +.TH SADF 1 "JULY 2018" Linux "Linux User's Manual" -*- nroff -*- +.SH NAME +sadf \- Display data collected by sar in multiple formats. +.SH SYNOPSIS +.B sadf [ -C ] [ -c | -d | -g | -j | -p | -r | -x ] [ -H ] [ -h ] [ -T | -t | -U ] [ -V ] [ -O +.I opts +.B [,...] ] [ -P { +.I cpu_list +.B | ALL } ] [ -s [ +.I hh:mm[:ss] +.B ] ] [ -e [ +.I hh:mm[:ss] +.B ] ] [ --dev= +.I dev_list +.B ] [ --fs= +.I fs_list +.B ] [ --iface= +.I iface_list +.B ] [ -- +.I sar_options +.B ] [ +.I interval +.B [ +.I count +.B ] ] [ +.I datafile +| +.I -[0-9]+ +.B ] +.SH DESCRIPTION +The +.B sadf +command is used for displaying the contents of data files created by the +.BR sar (1) +command. But unlike +.BR sar , +.B sadf +can write its data in many different formats (CSV, XML, etc.) +The default format is one that can +easily be handled by pattern processing commands like awk (see option -p). +The +.B sadf +command can also be used to draw graphs for the various activities collected +by +.B sar +and display them as SVG (Scalable Vector Graphics) graphics in your web browser +(see option -g). + +The +.B sadf +command extracts and writes to standard output records saved in the +.I datafile +file. This file must have been created by a version of +.B sar +which is compatible with that of +.B sadf. +If +.I datafile +is omitted, +.B sadf +uses the standard system activity daily data file. +It is also possible to enter -1, -2 etc. as an argument to +.B sadf +to display data of that days ago. +For example, -1 will point at the standard system +activity file of yesterday. + +The standard system activity daily data file is named +.I saDD +or +.IR saYYYYMMDD , +where YYYY stands for the current year, MM for the current month and +DD for the current day. +.B sadf +will look for the most recent of +.I saDD +and +.IR saYYYYMMDD , +and use it. By default it is located in the +.I /var/log/sa +directory. Yet it is possible to specify an alternate location for it: +If +.I datafile +is a directory (instead of a plain file) then it will be considered as +the directory where the standard system activity daily data file is +located. + +The +.I interval +and +.I count +parameters are used to tell +.B sadf +to select +.I count +records at +.I interval +seconds apart. If the +.I count +parameter is not set, then all the records saved in the data file will be +displayed. + +All the activity flags of +.B sar +may be entered on the command line to indicate which +activities are to be reported. Before specifying them, put a pair of +dashes (--) on the command line in order not to confuse the flags +with those of +.B sadf. +Not specifying any flags selects only CPU activity. + +.SH OPTIONS +.IP -C +Tell +.B sadf +to display comments present in file. +.IP -c +Convert an old system activity binary datafile (version 9.1.6 and later) +to current up-to-date format. Use the following syntax: + +.B sadf -c old_datafile > new_datafile + +.IP -d +Print the contents of the data file in a format that can easily +be ingested by a relational database system. The output consists +of fields separated by a semicolon. Each record contains +the hostname of the host where the file was created, the interval value +(or -1 if not applicable), the timestamp in a form easily acceptable by +most databases, and additional semicolon separated data fields as specified +by +.I sar_options +command line options. +Note that timestamp output can be controlled by options -T, -t and -U. +.IP --dev=dev_list +Specify the block devices for which statistics are to be displayed by +.BR sadf . +.IR dev_list +is a list of comma-separated device names. Useful with option -d from +.BR sar . +.IP "-e [ hh:mm[:ss] ]" +Set the ending time of the report, given in local time. The default ending +time is 18:00:00. Hours must be given in 24-hour format. +.IP --fs=fs_list +Specify the filesystems for which statistics are to be displayed by +.BR sadf . +.IR fs_list +is a list of comma-separated filesystem names or mountpoints. Useful with +option -F from +.BR sar . +.IP -g +Print the contents of the data file in SVG (Scalable Vector Graphics) format. +This option enables you to display some fancy graphs in your web browser. +Use the following syntax: + +.B sadf -g your_datafile [ -- +.I sar_options +.B ] > output.svg + +and open the resulting SVG file in your favorite web browser. +.IP -H +Display only the header of the report (when applicable). If no format has +been specified, then the header data (metadata) of the data file are displayed. +.IP -h +When used in conjunction with option -d, all activities +will be displayed horizontally on a single line. +.IP --iface=iface_list +Specify the network interfaces for which statistics are to be displayed by +.BR sadf . +.IR iface_list +is a list of comma-separated interface names. Useful with options -n DEV and +-n EDEV from +.BR sar . +.IP -j +Print the contents of the data file in JSON (JavaScript Object Notation) +format. Timestamps can be controlled by options -T and -t. +.IP "-O opts [,...]" +Use the specified options to control the output of +.BR sadf . +The following options are used to control SVG output displayed by +.BR "sadf -g": + +.B autoscale +.RS +.RS +Draw all the graphs of a given view as large as possible based on current +view's scale. To do this, a factor (10, 100, 1000...) is used to +enlarge the graph drawing. +This option may be interesting when several graphs are drawn on the same +view, some with only very small values, and others with high ones, +the latter making the former hardly visible. +.RE + +.BR height= value +.RS +Set SVG canvas height to +.IR value . +.RE + +.B oneday +.RS +Display graphs data over a period of 24 hours. Note that hours are still +printed in UTC by default: You should use option -T to print them in local +time and get a time window starting from midnight. +.RE + +.B packed +.RS +Group all views from the same activity (and for the same device) on the same row. +.RE + +.B showidle +.RS +Also display %idle state in graphs for CPU statistics. +.RE + +.B showinfo +.RS +Display additional information (such as the date and the host name) on each view. +.RE + +.B showtoc +.RS +Add a table of contents at the beginning of the SVG output, consisting of links +pointing at the first graph of each activity. +.RE + +.B skipempty +.RS +Do not display views where all graphs have only zero values. +.RE + +The following option is used to control raw output displayed by +.BR "sadf -r": + +.B debug +.RS +Display additional information, mainly useful for debugging purpose. +.RE +.RE +.IP "-P { cpu_list | ALL }" +Tell +.B sadf +that processor dependent statistics are to be reported only for the +specified processor or processors. +.I cpu_list +is a list of comma-separated values or range of values (e.g., +.BR 0,2,4-7,12- ). +Note that processor 0 is the first processor, and processor +.B all +is the global average among all processors. +Specifying the +.B ALL +keyword reports statistics for each individual processor, and globally for +all processors. +.IP -p +Print the contents of the data file in a format that can +easily be handled by pattern processing commands like awk. +The output consists of fields separated by a tab. Each record contains the +hostname of the host where the file was created, the interval value +(or -1 if not applicable), the timestamp, +the device name (or - if not applicable), +the field name and its value. +Note that timestamp output can be controlled by options -T, -t and -U. +.IP -r +Print the raw contents of the data file. With this format, the values for +all the counters are displayed as read from the kernel, which means e.g., that +no average values are calculated over the elapsed time interval. +.IP "-s [ hh:mm[:ss] ]" +Set the starting time of the data (given in local time), causing the +.B sadf +command to extract records time-tagged at, or following, the time +specified. The default starting time is 08:00:00. +Hours must be given in 24-hour format. +.IP -T +Display timestamp in local time instead of UTC (Coordinated Universal Time). +.IP -t +Display timestamp in the original local time of the data file creator +instead of UTC (Coordinated Universal Time). +.IP -U +Display timestamp (UTC - Coordinated Universal Time) in seconds from +the epoch. +.IP -V +Print version number then exit. +.IP -x +Print the contents of the data file in XML format. +Timestamps can be controlled by options -T and -t. +The corresponding +DTD (Document Type Definition) and XML Schema are included in the sysstat +source package. They are also available at +.I http://pagesperso-orange.fr/sebastien.godard/download.html + +.SH ENVIRONMENT +The +.B sadf +command takes into account the following environment variable: + +.IP S_TIME_DEF_TIME +If this variable exists and its value is +.BR UTC +then +.B sadf +will use UTC time instead of local time to determine the current daily data +file located in the +.IR /var/log/sa +directory. +.SH EXAMPLES +.B sadf -d /var/log/sa/sa21 -- -r -n DEV +.RS +Extract memory and network statistics from system activity +file 'sa21', and display them in a format that can be ingested by a +database. +.RE + +.B sadf -p -P 1 +.RS +Extract CPU statistics for processor 1 (the second processor) from current +daily data file, and display them in a format that can easily be handled +by a pattern processing command. +.RE + +.SH BUGS +SVG output (as created by option -g) is fully compliant with SVG 1.1 standard. +Graphics have been successfully displayed in various web browsers, including +Firefox, Chrome and Opera. Yet SVG rendering is broken on Microsoft browsers +(tested on Internet Explorer 11 and Edge 13.1): So please don't use them. + +.SH FILES +.I /var/log/sa/saDD +.br +.I /var/log/sa/saYYYYMMDD +.RS +The standard system activity daily data files and their default location. +YYYY stands for the current year, MM for the current month and DD for the +current day. + +.RE +.SH AUTHOR +Sebastien Godard (sysstat orange.fr) +.SH SEE ALSO +.BR sar (1), +.BR sadc (8), +.BR sa1 (8), +.BR sa2 (8), +.BR sysstat (5) + +.I https://github.com/sysstat/sysstat + +.I http://pagesperso-orange.fr/sebastien.godard/ diff --git a/manual/sysstat/original/man1/sar.1 b/manual/sysstat/original/man1/sar.1 new file mode 100644 index 00000000..410e1e3e --- /dev/null +++ b/manual/sysstat/original/man1/sar.1 @@ -0,0 +1,2427 @@ +.TH SAR 1 "APRIL 2019" Linux "Linux User's Manual" -*- nroff -*- +.SH NAME +sar \- Collect, report, or save system activity information. +.SH SYNOPSIS +.B sar [ -A ] [ -B ] [ -b ] [ -C ] [ -D ] [ -d ] [ -F [ MOUNT ] ] [ -H ] [ -h ] [ -p ] [ -q ] +.B [ -r [ ALL ] ] [ -S ] [ -t ] [ -u [ ALL ] ] [ -V ] [ -v ] [ -W ] [ -w ] [ -y ] [ -z ] +.B [ --dec={ 0 | 1 | 2 } ] [ --dev= +.I dev_list +.B ] [ --fs= +.I fs_list +.B ] [ --help ] [ --human ] [ --iface= +.I iface_list +.B ] [ --sadc ] +.B [ -I { +.I int_list +.B | SUM | ALL } ] [ -P { +.I cpu_list +.B | ALL } ] +.B [ -m { +.I keyword +.B [,...] | ALL } ] +.B [ -n { +.I keyword +.B [,...] | ALL } ] +.B [ -j { ID | LABEL | PATH | UUID | ... } ] +.B [ -f [ +.I filename +.B ] | -o [ +.I filename +.B ] | -[0-9]+ ] +.B [ -i +.I interval +.B ] [ -s [ +.I hh:mm[:ss] +.B ] ] [ -e [ +.I hh:mm[:ss] +.B ] ] [ +.I interval +.B [ +.I count +.B ] ] +.SH DESCRIPTION +The +.B sar +command writes to standard output the contents of selected +cumulative activity counters in the operating system. The accounting +system, based on the values in the +.I count +and +.I interval +parameters, writes information the specified number of times spaced +at the specified intervals in seconds. +If the +.I interval +parameter is set to zero, the +.B sar +command displays the average statistics for the time +since the system was started. If the +.I interval +parameter is specified without the +.I count +parameter, then reports are generated continuously. +The collected data can also +be saved in the file specified by the -o +.I filename +flag, in addition to being displayed onto the screen. If +.I filename +is omitted, +.B sar +uses the standard system activity daily data file (see below). +By default all the data available from the kernel are saved in the +data file. + +The +.B sar +command extracts and writes to standard output records previously +saved in a file. This file can be either the one specified by the +-f flag or, by default, the standard system activity daily data file. +It is also possible to enter -1, -2 etc. as an argument to +.B sar +to display data +of that days ago. For example, -1 will point at the standard system +activity file of yesterday. + +Standard system activity daily data files are named +.I saDD +or +.IR saYYYYMMDD , +where YYYY stands for the current year, MM for the current month and +DD for the current day. They are the default files used by +.B sar +only when no filename has been explicitly specified. +When used to write data to files (with its option -o), +.B sar +will use +.I saYYYYMMDD +if option -D has also been specified, else it will use +.IR saDD . +When used to display the records previously saved in a file, +.B sar +will look for the most recent of +.I saDD +and +.IR saYYYYMMDD , +and use it. + +Standard system activity daily data files are located in the +.I /var/log/sa +directory by default. Yet it is possible to specify an alternate +location for them: If a directory (instead of a plain file) is used +with options -f or -o +then it will be considered as the directory containing the data files. + +Without the -P flag, the +.B sar +command reports system-wide (global among all processors) statistics, +which are calculated as averages for values expressed as percentages, +and as sums otherwise. If the -P +flag is given, the +.B sar +command reports activity which relates to the specified processor or +processors. If -P ALL +is given, the +.B sar +command reports statistics for each individual processor and global +statistics among all processors. Offline processors are not displayed. + +You can select information about specific system activities using +flags. Not specifying any flags selects only CPU activity. +Specifying the -A +flag selects all possible activities. + +The default version of the +.B sar +command (CPU utilization report) might be one of the first facilities +the user runs to begin system activity investigation, because it +monitors major system resources. If CPU utilization is near 100 percent +(user + nice + system), the workload sampled is CPU-bound. + +If multiple samples and multiple reports are desired, it is convenient +to specify an output file for the +.B sar +command. +Run the +.B sar +command as a background process. The syntax for this is: + +.B sar -o datafile interval count >/dev/null 2>&1 & + +All data are captured in binary form and saved to a file (datafile). +The data can then be selectively displayed with the +.B sar +command using the -f +option. Set the +.I interval +and +.I count +parameters to select +.I count +records at +.I interval +second intervals. If the +.I count +parameter is not set, all the records saved in the +file will be selected. +Collection of data in this manner is useful to characterize +system usage over a period of time and determine peak usage hours. + +Note: The +.B sar +command only reports on local activities. + +.SH OPTIONS +.IP -A +This is equivalent to specifying +.BR "-bBdFHqSvwWy -I SUM -I ALL -m ALL -n ALL -r ALL -u ALL -P ALL". +.IP -B +Report paging statistics. +The following values are displayed: + +.B pgpgin/s +.RS +.RS +Total number of kilobytes the system paged in from disk per second. +.RE + +.B pgpgout/s +.RS +Total number of kilobytes the system paged out to disk per second. +.RE + +.B fault/s +.RS +Number of page faults (major + minor) made by the system per second. +This is not a count of page faults that generate I/O, because some page +faults can be resolved without I/O. +.RE + +.B majflt/s +.RS +Number of major faults the system has made per second, those which +have required loading a memory page from disk. +.RE + +.B pgfree/s +.RS +Number of pages placed on the free list by the system per second. +.RE + +.B pgscank/s +.RS +Number of pages scanned by the kswapd daemon per second. +.RE + +.B pgscand/s +.RS +Number of pages scanned directly per second. +.RE + +.B pgsteal/s +.RS +Number of pages the system has reclaimed from cache (pagecache and +swapcache) per second to satisfy its memory demands. +.RE + +.B %vmeff +.RS +Calculated as pgsteal / pgscan, this is a metric of the efficiency of +page reclaim. If it is near 100% then almost every page coming off the +tail of the inactive list is being reaped. If it gets too low (e.g. less +than 30%) then the virtual memory is having some difficulty. +This field is displayed as zero if no pages have been scanned during the +interval of time. +.RE +.RE +.IP -b +Report I/O and transfer rate statistics. +The following values are displayed: + +.B tps +.RS +.RS +Total number of transfers per second that were issued to physical devices. +A transfer is an I/O request to a physical device. Multiple logical +requests can be combined into a single I/O request to the device. +A transfer is of indeterminate size. +.RE + +.B rtps +.RS +Total number of read requests per second issued to physical devices. +.RE + +.B wtps +.RS +Total number of write requests per second issued to physical devices. +.RE + +.B bread/s +.RS +Total amount of data read from the devices in blocks per second. +Blocks are equivalent to sectors +and therefore have a size of 512 bytes. +.RE + +.B bwrtn/s +.RS +Total amount of data written to devices in blocks per second. +.RE +.RE +.IP -C +When reading data from a file, tell +.B sar +to display comments that have been inserted by +.BR sadc . +.IP -D +Use +.I saYYYYMMDD +instead of +.I saDD +as the standard system activity daily data file name. This option +works only when used in conjunction with option -o +to save data to file. +.IP -d +Report activity for each block device. +When data are displayed, the device specification +.I devM-n +is generally used (DEV column). +M is the major number of the device and n +its minor number. +Device names may also be pretty-printed if option -p +is used or persistent device names can be printed if option -j is used +(see below). Statistics for all devices are displayed unless +a restricted list is specified using option +.BR --dev= +(see corresponding option entry). +Note that disk activity depends on +.B sadc +options +.B "-S DISK" +and +.B "-S XDISK" +to be collected. The following values are displayed: + +.B tps +.RS +.RS +Total number of transfers per second that were issued to physical devices. +A transfer is an I/O request to a physical device. Multiple logical +requests can be combined into a single I/O request to the device. +A transfer is of indeterminate size. +.RE + +.B rkB/s +.RS +Number of kilobytes read from the device per second. +.RE + +.B wkB/s +.RS +Number of kilobytes written to the device per second. +.RE + +.B areq-sz +.RS +The average size (in kilobytes) of the I/O requests that were issued to the device. +.br +Note: In previous versions, this field was known as avgrq-sz and was expressed in sectors. +.RE + +.B aqu-sz +.RS +The average queue length of the requests that were issued to the device. +.br +Note: In previous versions, this field was known as avgqu-sz. +.RE + +.B await +.RS +The average time (in milliseconds) for I/O requests issued to the device +to be served. This includes the time spent by the requests in queue and +the time spent servicing them. +.RE + +.B svctm +.RS +The average service time (in milliseconds) for I/O requests that were issued +to the device. Warning! Do not trust this field any more. This field will be +removed in a future sysstat version. +.RE + +.B %util +.RS +Percentage of elapsed time during which I/O requests were issued to the device +(bandwidth utilization for the device). Device saturation occurs when this +value is close to 100% for devices serving requests serially. But for +devices serving requests in parallel, such as RAID arrays and modern SSDs, +this number does not reflect their performance limits. +.RE +.RE +.IP "--dec={ 0 | 1 | 2 }" +Specify the number of decimal places to use (0 to 2, default value is 2). +.IP --dev=dev_list +Specify the block devices for which statistics are to be displayed by +.BR sar . +.IR dev_list +is a list of comma-separated device names. +.IP "-e [ hh:mm[:ss] ]" +Set the ending time of the report. The default ending time is +18:00:00. Hours must be given in 24-hour format. +This option can be used when data are read from +or written to a file (options -f or -o). +.IP "-F [ MOUNT ]" +Display statistics for currently mounted filesystems. Pseudo-filesystems are +ignored. At the end of the report, +.B sar +will display a summary of all those filesystems. +Use of the +.B MOUNT +parameter keyword indicates that mountpoint will be reported instead of +filesystem device. Statistics for all filesystems are displayed unless +a restricted list is specified using option +.BR --fs= +(see corresponding option entry). +Note that filesystems statistics depend on +.B sadc +option +.B "-S XDISK" +to be collected. + +The following values are displayed: + +.B MBfsfree +.RS +.RS +Total amount of free space in megabytes (including space available only to privileged user). +.RE + +.B MBfsused +.RS +Total amount of space used in megabytes. +.RE + +.B %fsused +.RS +Percentage of filesystem space used, as seen by a privileged user. +.RE + +.B %ufsused +.RS +Percentage of filesystem space used, as seen by an unprivileged user. +.RE + +.B Ifree +.RS +Total number of free file nodes in filesystem. +.RE + +.B Iused +.RS +Total number of file nodes used in filesystem. +.RE + +.B %Iused +.RS +Percentage of file nodes used in filesystem. +.RE +.RE +.IP "-f [ filename ]" +Extract records from +.I filename +(created by the -o +.I filename +flag). The default value of the +.I filename +parameter is the current standard system activity daily data file. +If +.I filename +is a directory instead of a plain file then it is considered as the +directory where the standard system activity daily data files are +located. The -f option is exclusive of the -o option. +.IP --fs=fs_list +Specify the filesystems for which statistics are to be displayed by +.BR sar . +.IR fs_list +is a list of comma-separated filesystem names or mountpoints. +.IP -H +Report hugepages utilization statistics. +The following values are displayed: + +.B kbhugfree +.RS +.RS +Amount of hugepages memory in kilobytes that is not yet allocated. +.RE + +.B kbhugused +.RS +Amount of hugepages memory in kilobytes that has been allocated. +.RE + +.B %hugused +.RS +Percentage of total hugepages memory that has been allocated. +.RE +.RE +.IP -h +Make the output of sar easier to read by a human. Options +.B --human +and +.B -p +(pretty-print) are enabled implicitly with this option. +This option may be especially useful when displaying e.g., network interfaces +or block devices statistics. +.IP --help +Display a short help message then exit. +.IP --human +Print sizes in human readable format (e.g. 1.0k, 1.2M, etc.) +The units displayed with this option supersede any other default units (e.g. +kilobytes, sectors...) associated with the metrics. +.IP "-I { int_list | SUM | ALL }" +Report statistics for interrupts. +.I int_list +is a list of comma-separated values or range of values (e.g., +.BR 0-16,35,400- ). +The +.B SUM +keyword indicates that the total number of interrupts received per second +is to be displayed. The +.B ALL +keyword indicates that statistics from all interrupts, including potential +APIC interrupt sources, are to be reported. +Note that interrupt statistics depend on +.B sadc +option "-S INT" +to be collected. +.IP "-i interval" +Select data records at seconds as close as possible to the number specified +by the +.I interval +parameter. +.IP --iface=iface_list +Specify the network interfaces for which statistics are to be displayed by +.BR sar . +.IR iface_list +is a list of comma-separated interface names. +.IP "-j { ID | LABEL | PATH | UUID | ... }" +Display persistent device names. Use this option in conjunction with option -d. +Options +.BR ID , +.BR LABEL , +etc. specify the type of the persistent name. These options are not limited, +only prerequisite is that directory with required persistent names is present in +.IR /dev/disk . +If persistent name is not found for the device, the device name +is pretty-printed (see option -p below). +.IP "-m { keyword [,...] | ALL }" +Report power management statistics. +Note that these statistics depend on +.BR sadc 's +option "-S POWER" to be collected. + +Possible keywords are +.BR CPU , +.BR FAN , +.BR FREQ , +.BR IN , +.BR TEMP +and +.BR USB . + +With the +.B CPU +keyword, statistics about CPU are reported. +The following value is displayed: + +.B MHz +.RS +.RS +Instantaneous CPU clock frequency in MHz. +.RE + +With the +.B FAN +keyword, statistics about fans speed are reported. +The following values are displayed: + +.B rpm +.RS +Fan speed expressed in revolutions per minute. +.RE + +.B drpm +.RS +This field is calculated as the difference between current fan speed (rpm) +and its low limit (fan_min). +.RE + +.B DEVICE +.RS +Sensor device name. +.RE + +With the +.B FREQ +keyword, statistics about CPU clock frequency are reported. +The following value is displayed: + +.B wghMHz +.RS +Weighted average CPU clock frequency in MHz. +Note that the cpufreq-stats driver must be compiled in the +kernel for this option to work. +.RE + +With the +.B IN +keyword, statistics about voltage inputs are reported. +The following values are displayed: + +.B inV +.RS +Voltage input expressed in Volts. +.RE + +.B %in +.RS +Relative input value. A value of 100% means that +voltage input has reached its high limit (in_max) whereas +a value of 0% means that it has reached its low limit (in_min). +.RE + +.B DEVICE +.RS +Sensor device name. +.RE + +With the +.B TEMP +keyword, statistics about devices temperature are reported. +The following values are displayed: + +.B degC +.RS +Device temperature expressed in degrees Celsius. +.RE + +.B %temp +.RS +Relative device temperature. A value of 100% means that +temperature has reached its high limit (temp_max). +.RE + +.B DEVICE +.RS +Sensor device name. +.RE + +With the +.B USB +keyword, the +.B sar +command takes a snapshot of all the USB devices currently plugged into +the system. At the end of the report, +.B sar +will display a summary of all those USB devices. +The following values are displayed: + +.B BUS +.RS +Root hub number of the USB device. +.RE + +.B idvendor +.RS +Vendor ID number (assigned by USB organization). +.RE + +.B idprod +.RS +Product ID number (assigned by Manufacturer). +.RE + +.B maxpower +.RS +Maximum power consumption of the device (expressed in mA). +.RE + +.B manufact +.RS +Manufacturer name. +.RE + +.B product +.RS +Product name. +.RE + +The +.B ALL +keyword is equivalent to specifying all the keywords above and therefore all the power +management statistics are reported. +.RE +.RE +.IP "-n { keyword [,...] | ALL }" +Report network statistics. + +Possible keywords are +.BR DEV , +.BR EDEV , +.BR FC , +.BR ICMP , +.BR EICMP , +.BR ICMP6 , +.BR EICMP6 , +.BR IP , +.BR EIP , +.BR IP6 , +.BR EIP6 , +.BR NFS , +.BR NFSD , +.BR SOCK , +.BR SOCK6 , +.BR SOFT , +.BR TCP , +.BR ETCP , +.BR UDP +and +.BR UDP6 . + +With the +.B DEV +keyword, statistics from the network devices are reported. +Statistics for all network interfaces are displayed unless +a restricted list is specified using option +.BR --iface= +(see corresponding option entry). +The following values are displayed: + +.B IFACE +.RS +.RS +Name of the network interface for which statistics are reported. +.RE + +.B rxpck/s +.RS +Total number of packets received per second. +.RE + +.B txpck/s +.RS +Total number of packets transmitted per second. +.RE + +.B rxkB/s +.RS +Total number of kilobytes received per second. +.RE + +.B txkB/s +.RS +Total number of kilobytes transmitted per second. +.RE + +.B rxcmp/s +.RS +Number of compressed packets received per second (for cslip etc.). +.RE + +.B txcmp/s +.RS +Number of compressed packets transmitted per second. +.RE + +.B rxmcst/s +.RS +Number of multicast packets received per second. +.RE + +.B %ifutil +.RS +Utilization percentage of the network interface. For half-duplex interfaces, +utilization is calculated using the sum of rxkB/s and txkB/s as a percentage +of the interface speed. For full-duplex, this is the greater of rxkB/S or txkB/s. +.RE + +With the +.B EDEV +keyword, statistics on failures (errors) from the network devices are reported. +Statistics for all network interfaces are displayed unless +a restricted list is specified using option +.BR --iface= +(see corresponding option entry). +The following values are displayed: + +.B IFACE +.RS +Name of the network interface for which statistics are reported. +.RE + +.B rxerr/s +.RS +Total number of bad packets received per second. +.RE + +.B txerr/s +.RS +Total number of errors that happened per second while transmitting packets. +.RE + +.B coll/s +.RS +Number of collisions that happened per second while transmitting packets. +.RE + +.B rxdrop/s +.RS +Number of received packets dropped per second because of a lack of space in linux buffers. +.RE + +.B txdrop/s +.RS +Number of transmitted packets dropped per second because of a lack of space in linux buffers. +.RE + +.B txcarr/s +.RS +Number of carrier-errors that happened per second while transmitting packets. +.RE + +.B rxfram/s +.RS +Number of frame alignment errors that happened per second on received packets. +.RE + +.B rxfifo/s +.RS +Number of FIFO overrun errors that happened per second on received packets. +.RE + +.B txfifo/s +.RS +Number of FIFO overrun errors that happened per second on transmitted packets. +.RE + +With the +.B FC +keyword, statistics about fibre channel traffic are reported. +Note that fibre channel statistics depend on +.BR sadc 's +option "-S DISK" to be collected. +The following values are displayed: + +.B FCHOST +.RS +Name of the fibre channel host bus adapter (HBA) interface for which statistics are reported. +.RE + +.B fch_rxf/s +.RS +The total number of frames received per second. +.RE + +.B fch_txf/s +.RS +The total number of frames transmitted per second. +.RE + +.B fch_rxw/s +.RS +The total number of transmission words received per second. +.RE + +.B fch_txw/s +.RS +The total number of transmission words transmitted per second. +.RE + +With the +.B ICMP +keyword, statistics about ICMPv4 network traffic are reported. +Note that ICMPv4 statistics depend on +.BR sadc 's +option "-S SNMP" +to be collected. +The following values are displayed (formal SNMP names between +square brackets): + +.B imsg/s +.RS +The total number of ICMP messages which the entity +received per second [icmpInMsgs]. +Note that this counter includes all those counted by ierr/s. +.RE + +.B omsg/s +.RS +The total number of ICMP messages which this entity +attempted to send per second [icmpOutMsgs]. +Note that this counter includes all those counted by oerr/s. +.RE + +.B iech/s +.RS +The number of ICMP Echo (request) messages received per second [icmpInEchos]. +.RE + +.B iechr/s +.RS +The number of ICMP Echo Reply messages received per second [icmpInEchoReps]. +.RE + +.B oech/s +.RS +The number of ICMP Echo (request) messages sent per second [icmpOutEchos]. +.RE + +.B oechr/s +.RS +The number of ICMP Echo Reply messages sent per second [icmpOutEchoReps]. +.RE + +.B itm/s +.RS +The number of ICMP Timestamp (request) messages received per second [icmpInTimestamps]. +.RE + +.B itmr/s +.RS +The number of ICMP Timestamp Reply messages received per second [icmpInTimestampReps]. +.RE + +.B otm/s +.RS +The number of ICMP Timestamp (request) messages sent per second [icmpOutTimestamps]. +.RE + +.B otmr/s +.RS +The number of ICMP Timestamp Reply messages sent per second [icmpOutTimestampReps]. +.RE + +.B iadrmk/s +.RS +The number of ICMP Address Mask Request messages received per second [icmpInAddrMasks]. +.RE + +.B iadrmkr/s +.RS +The number of ICMP Address Mask Reply messages received per second [icmpInAddrMaskReps]. +.RE + +.B oadrmk/s +.RS +The number of ICMP Address Mask Request messages sent per second [icmpOutAddrMasks]. +.RE + +.B oadrmkr/s +.RS +The number of ICMP Address Mask Reply messages sent per second [icmpOutAddrMaskReps]. +.RE + +With the +.B EICMP +keyword, statistics about ICMPv4 error messages are reported. +Note that ICMPv4 statistics depend on +.BR sadc 's +option "-S SNMP" to be collected. +The following values are displayed (formal SNMP names between +square brackets): + +.B ierr/s +.RS +The number of ICMP messages per second which the entity received but +determined as having ICMP-specific errors (bad ICMP +checksums, bad length, etc.) [icmpInErrors]. +.RE + +.B oerr/s +.RS +The number of ICMP messages per second which this entity did not send +due to problems discovered within ICMP such as a lack of buffers [icmpOutErrors]. +.RE + +.B idstunr/s +.RS +The number of ICMP Destination Unreachable messages +received per second [icmpInDestUnreachs]. +.RE + +.B odstunr/s +.RS +The number of ICMP Destination Unreachable messages sent per second [icmpOutDestUnreachs]. +.RE + +.B itmex/s +.RS +The number of ICMP Time Exceeded messages received per second [icmpInTimeExcds]. +.RE + +.B otmex/s +.RS +The number of ICMP Time Exceeded messages sent per second [icmpOutTimeExcds]. +.RE + +.B iparmpb/s +.RS +The number of ICMP Parameter Problem messages received per second [icmpInParmProbs]. +.RE + +.B oparmpb/s +.RS +The number of ICMP Parameter Problem messages sent per second [icmpOutParmProbs]. +.RE + +.B isrcq/s +.RS +The number of ICMP Source Quench messages received per second [icmpInSrcQuenchs]. +.RE + +.B osrcq/s +.RS +The number of ICMP Source Quench messages sent per second [icmpOutSrcQuenchs]. +.RE + +.B iredir/s +.RS +The number of ICMP Redirect messages received per second [icmpInRedirects]. +.RE + +.B oredir/s +.RS +The number of ICMP Redirect messages sent per second [icmpOutRedirects]. +.RE + +With the +.B ICMP6 +keyword, statistics about ICMPv6 network traffic are reported. +Note that ICMPv6 statistics depend on +.BR sadc 's +option "-S IPV6" to be collected. +The following values are displayed (formal SNMP names between +square brackets): + +.B imsg6/s +.RS +The total number of ICMP messages received +by the interface per second which includes all those +counted by ierr6/s [ipv6IfIcmpInMsgs]. +.RE + +.B omsg6/s +.RS +The total number of ICMP messages which this +interface attempted to send per second [ipv6IfIcmpOutMsgs]. +.RE + +.B iech6/s +.RS +The number of ICMP Echo (request) messages +received by the interface per second [ipv6IfIcmpInEchos]. +.RE + +.B iechr6/s +.RS +The number of ICMP Echo Reply messages received +by the interface per second [ipv6IfIcmpInEchoReplies]. +.RE + +.B oechr6/s +.RS +The number of ICMP Echo Reply messages sent +by the interface per second [ipv6IfIcmpOutEchoReplies]. +.RE + +.B igmbq6/s +.RS +The number of ICMPv6 Group Membership Query +messages received by the interface per second +[ipv6IfIcmpInGroupMembQueries]. +.RE + +.B igmbr6/s +.RS +The number of ICMPv6 Group Membership Response messages +received by the interface per second +[ipv6IfIcmpInGroupMembResponses]. +.RE + +.B ogmbr6/s +.RS +The number of ICMPv6 Group Membership Response +messages sent per second +[ipv6IfIcmpOutGroupMembResponses]. +.RE + +.B igmbrd6/s +.RS +The number of ICMPv6 Group Membership Reduction messages +received by the interface per second +[ipv6IfIcmpInGroupMembReductions]. +.RE + +.B ogmbrd6/s +.RS +The number of ICMPv6 Group Membership Reduction +messages sent per second +[ipv6IfIcmpOutGroupMembReductions]. +.RE + +.B irtsol6/s +.RS +The number of ICMP Router Solicit messages +received by the interface per second +[ipv6IfIcmpInRouterSolicits]. +.RE + +.B ortsol6/s +.RS +The number of ICMP Router Solicitation messages +sent by the interface per second +[ipv6IfIcmpOutRouterSolicits]. +.RE + +.B irtad6/s +.RS +The number of ICMP Router Advertisement messages +received by the interface per second +[ipv6IfIcmpInRouterAdvertisements]. +.RE + +.B inbsol6/s +.RS +The number of ICMP Neighbor Solicit messages +received by the interface per second +[ipv6IfIcmpInNeighborSolicits]. +.RE + +.B onbsol6/s +.RS +The number of ICMP Neighbor Solicitation +messages sent by the interface per second +[ipv6IfIcmpOutNeighborSolicits]. +.RE + +.B inbad6/s +.RS +The number of ICMP Neighbor Advertisement +messages received by the interface per second +[ipv6IfIcmpInNeighborAdvertisements]. +.RE + +.B onbad6/s +.RS +The number of ICMP Neighbor Advertisement +messages sent by the interface per second +[ipv6IfIcmpOutNeighborAdvertisements]. +.RE + +With the +.B EICMP6 +keyword, statistics about ICMPv6 error messages are reported. +Note that ICMPv6 statistics depend on +.BR sadc 's +option "-S IPV6" to be collected. +The following values are displayed (formal SNMP names between +square brackets): + +.B ierr6/s +.RS +The number of ICMP messages per second which the interface +received but determined as having ICMP-specific +errors (bad ICMP checksums, bad length, etc.) +[ipv6IfIcmpInErrors] +.RE + +.B idtunr6/s +.RS +The number of ICMP Destination Unreachable +messages received by the interface per second +[ipv6IfIcmpInDestUnreachs]. +.RE + +.B odtunr6/s +.RS +The number of ICMP Destination Unreachable +messages sent by the interface per second +[ipv6IfIcmpOutDestUnreachs]. +.RE + +.B itmex6/s +.RS +The number of ICMP Time Exceeded messages +received by the interface per second +[ipv6IfIcmpInTimeExcds]. +.RE + +.B otmex6/s +.RS +The number of ICMP Time Exceeded messages sent +by the interface per second +[ipv6IfIcmpOutTimeExcds]. +.RE + +.B iprmpb6/s +.RS +The number of ICMP Parameter Problem messages +received by the interface per second +[ipv6IfIcmpInParmProblems]. +.RE + +.B oprmpb6/s +.RS +The number of ICMP Parameter Problem messages +sent by the interface per second +[ipv6IfIcmpOutParmProblems]. +.RE + +.B iredir6/s +.RS +The number of Redirect messages received +by the interface per second +[ipv6IfIcmpInRedirects]. +.RE + +.B oredir6/s +.RS +The number of Redirect messages sent by +the interface by second +[ipv6IfIcmpOutRedirects]. +.RE + +.B ipck2b6/s +.RS +The number of ICMP Packet Too Big messages +received by the interface per second +[ipv6IfIcmpInPktTooBigs]. +.RE + +.B opck2b6/s +.RS +The number of ICMP Packet Too Big messages sent +by the interface per second +[ipv6IfIcmpOutPktTooBigs]. +.RE + +With the +.B IP +keyword, statistics about IPv4 network traffic are reported. +Note that IPv4 statistics depend on +.BR sadc 's +option "-S SNMP" +to be collected. +The following values are displayed (formal SNMP names between +square brackets): + +.B irec/s +.RS +The total number of input datagrams received from interfaces +per second, including those received in error [ipInReceives]. +.RE + +.B fwddgm/s +.RS +The number of input datagrams per second, for which this entity was not +their final IP destination, as a result of which an attempt +was made to find a route to forward them to that final +destination [ipForwDatagrams]. +.RE + +.B idel/s +.RS +The total number of input datagrams successfully delivered per second +to IP user-protocols (including ICMP) [ipInDelivers]. +.RE + +.B orq/s +.RS +The total number of IP datagrams which local IP user-protocols (including ICMP) +supplied per second to IP in requests for transmission [ipOutRequests]. +Note that this counter does not include any datagrams counted in fwddgm/s. +.RE + +.B asmrq/s +.RS +The number of IP fragments received per second which needed to be +reassembled at this entity [ipReasmReqds]. +.RE + +.B asmok/s +.RS +The number of IP datagrams successfully re-assembled per second [ipReasmOKs]. +.RE + +.B fragok/s +.RS +The number of IP datagrams that have been successfully +fragmented at this entity per second [ipFragOKs]. +.RE + +.B fragcrt/s +.RS +The number of IP datagram fragments that have been +generated per second as a result of fragmentation at this entity [ipFragCreates]. +.RE + +With the +.B EIP +keyword, statistics about IPv4 network errors are reported. +Note that IPv4 statistics depend on +.BR sadc 's +option "-S SNMP" to be collected. +The following values are displayed (formal SNMP names between +square brackets): + +.B ihdrerr/s +.RS +The number of input datagrams discarded per second due to errors in +their IP headers, including bad checksums, version number +mismatch, other format errors, time-to-live exceeded, errors +discovered in processing their IP options, etc. [ipInHdrErrors] +.RE + +.B iadrerr/s +.RS +The number of input datagrams discarded per second because the IP +address in their IP header's destination field was not a +valid address to be received at this entity. This count +includes invalid addresses (e.g., 0.0.0.0) and addresses of +unsupported Classes (e.g., Class E). For entities which are +not IP routers and therefore do not forward datagrams, this +counter includes datagrams discarded because the destination +address was not a local address [ipInAddrErrors]. +.RE + +.B iukwnpr/s +.RS +The number of locally-addressed datagrams received +successfully but discarded per second because of an unknown or +unsupported protocol [ipInUnknownProtos]. +.RE + +.B idisc/s +.RS +The number of input IP datagrams per second for which no problems were +encountered to prevent their continued processing, but which +were discarded (e.g., for lack of buffer space) [ipInDiscards]. +Note that this counter does not include any datagrams discarded while +awaiting re-assembly. +.RE + +.B odisc/s +.RS +The number of output IP datagrams per second for which no problem was +encountered to prevent their transmission to their +destination, but which were discarded (e.g., for lack of +buffer space) [ipOutDiscards]. +Note that this counter would include +datagrams counted in fwddgm/s if any such packets met +this (discretionary) discard criterion. +.RE + +.B onort/s +.RS +The number of IP datagrams discarded per second because no route could +be found to transmit them to their destination [ipOutNoRoutes]. +Note that this counter includes any packets counted in fwddgm/s +which meet this 'no-route' criterion. +Note that this includes any datagrams which a host cannot route because all +of its default routers are down. +.RE + +.B asmf/s +.RS +The number of failures detected per second by the IP re-assembly +algorithm (for whatever reason: timed out, errors, etc) [ipReasmFails]. +Note that this is not necessarily a count of discarded IP +fragments since some algorithms can lose track of the number of +fragments by combining them as they are received. +.RE + +.B fragf/s +.RS +The number of IP datagrams that have been discarded per second because +they needed to be fragmented at this entity but could not +be, e.g., because their Don't Fragment flag was set [ipFragFails]. +.RE + +With the +.B IP6 +keyword, statistics about IPv6 network traffic are reported. +Note that IPv6 statistics depend on +.BR sadc 's +option "-S IPV6" to be collected. +The following values are displayed (formal SNMP names between +square brackets): + +.B irec6/s +.RS +The total number of input datagrams received from +interfaces per second, including those received in error +[ipv6IfStatsInReceives]. +.RE + +.B fwddgm6/s +.RS +The number of output datagrams per second which this +entity received and forwarded to their final +destinations [ipv6IfStatsOutForwDatagrams]. +.RE + +.B idel6/s +.RS +The total number of datagrams successfully +delivered per second to IPv6 user-protocols (including ICMP) +[ipv6IfStatsInDelivers]. +.RE + +.B orq6/s +.RS +The total number of IPv6 datagrams which local IPv6 +user-protocols (including ICMP) supplied per second to IPv6 in +requests for transmission [ipv6IfStatsOutRequests]. +Note that this counter +does not include any datagrams counted in fwddgm6/s. +.RE + +.B asmrq6/s +.RS +The number of IPv6 fragments received per second which needed +to be reassembled at this interface [ipv6IfStatsReasmReqds]. +.RE + +.B asmok6/s +.RS +The number of IPv6 datagrams successfully +reassembled per second [ipv6IfStatsReasmOKs]. +.RE + +.B imcpck6/s +.RS +The number of multicast packets received per second +by the interface [ipv6IfStatsInMcastPkts]. +.RE + +.B omcpck6/s +.RS +The number of multicast packets transmitted per second +by the interface [ipv6IfStatsOutMcastPkts]. +.RE + +.B fragok6/s +.RS +The number of IPv6 datagrams that have been +successfully fragmented at this output interface per second +[ipv6IfStatsOutFragOKs]. +.RE + +.B fragcr6/s +.RS +The number of output datagram fragments that have +been generated per second as a result of fragmentation at +this output interface [ipv6IfStatsOutFragCreates]. +.RE + +With the +.B EIP6 +keyword, statistics about IPv6 network errors are reported. +Note that IPv6 statistics depend on +.BR sadc 's +option "-S IPV6" to be collected. +The following values are displayed (formal SNMP names between +square brackets): + +.B ihdrer6/s +.RS +The number of input datagrams discarded per second due to +errors in their IPv6 headers, including version +number mismatch, other format errors, hop count +exceeded, errors discovered in processing their +IPv6 options, etc. [ipv6IfStatsInHdrErrors] +.RE + +.B iadrer6/s +.RS +The number of input datagrams discarded per second because +the IPv6 address in their IPv6 header's destination +field was not a valid address to be received at +this entity. This count includes invalid +addresses (e.g., ::0) and unsupported addresses +(e.g., addresses with unallocated prefixes). For +entities which are not IPv6 routers and therefore +do not forward datagrams, this counter includes +datagrams discarded because the destination address +was not a local address [ipv6IfStatsInAddrErrors]. +.RE + +.B iukwnp6/s +.RS +The number of locally-addressed datagrams +received successfully but discarded per second because of an +unknown or unsupported protocol [ipv6IfStatsInUnknownProtos]. +.RE + +.B i2big6/s +.RS +The number of input datagrams that could not be +forwarded per second because their size exceeded the link MTU +of outgoing interface [ipv6IfStatsInTooBigErrors]. +.RE + +.B idisc6/s +.RS +The number of input IPv6 datagrams per second for which no +problems were encountered to prevent their +continued processing, but which were discarded +(e.g., for lack of buffer space) +[ipv6IfStatsInDiscards]. Note that this +counter does not include any datagrams discarded +while awaiting re-assembly. +.RE + +.B odisc6/s +.RS +The number of output IPv6 datagrams per second for which no +problem was encountered to prevent their +transmission to their destination, but which were +discarded (e.g., for lack of buffer space) +[ipv6IfStatsOutDiscards]. Note +that this counter would include datagrams counted +in fwddgm6/s if any such packets +met this (discretionary) discard criterion. +.RE + +.B inort6/s +.RS +The number of input datagrams discarded per second because no +route could be found to transmit them to their +destination [ipv6IfStatsInNoRoutes]. +.RE + +.B onort6/s +.RS +The number of locally generated IP datagrams discarded per second +because no route could be found to transmit them to their +destination [unknown formal SNMP name]. +.RE + +.B asmf6/s +.RS +The number of failures detected per second by the IPv6 +re-assembly algorithm (for whatever reason: timed +out, errors, etc.) [ipv6IfStatsReasmFails]. +Note that this is not +necessarily a count of discarded IPv6 fragments +since some algorithms +can lose track of the number of fragments +by combining them as they are received. +.RE + +.B fragf6/s +.RS +The number of IPv6 datagrams that have been +discarded per second because they needed to be fragmented +at this output interface but could not be +[ipv6IfStatsOutFragFails]. +.RE + +.B itrpck6/s +.RS +The number of input datagrams discarded per second because +datagram frame didn't carry enough data +[ipv6IfStatsInTruncatedPkts]. +.RE + +With the +.B NFS +keyword, statistics about NFS client activity are reported. +The following values are displayed: + +.B call/s +.RS +Number of RPC requests made per second. +.RE + +.B retrans/s +.RS +Number of RPC requests per second, those which needed to be retransmitted (for +example because of a server timeout). +.RE + +.B read/s +.RS +Number of 'read' RPC calls made per second. +.RE + +.B write/s +.RS +Number of 'write' RPC calls made per second. +.RE + +.B access/s +.RS +Number of 'access' RPC calls made per second. +.RE + +.B getatt/s +.RS +Number of 'getattr' RPC calls made per second. +.RE + +With the +.B NFSD +keyword, statistics about NFS server activity are reported. +The following values are displayed: + +.B scall/s +.RS +Number of RPC requests received per second. +.RE + +.B badcall/s +.RS +Number of bad RPC requests received per second, those whose +processing generated an error. +.RE + +.B packet/s +.RS +Number of network packets received per second. +.RE + +.B udp/s +.RS +Number of UDP packets received per second. +.RE + +.B tcp/s +.RS +Number of TCP packets received per second. +.RE + +.B hit/s +.RS +Number of reply cache hits per second. +.RE + +.B miss/s +.RS +Number of reply cache misses per second. +.RE + +.B sread/s +.RS +Number of 'read' RPC calls received per second. +.RE + +.B swrite/s +.RS +Number of 'write' RPC calls received per second. +.RE + +.B saccess/s +.RS +Number of 'access' RPC calls received per second. +.RE + +.B sgetatt/s +.RS +Number of 'getattr' RPC calls received per second. +.RE + +With the +.B SOCK +keyword, statistics on sockets in use are reported +(IPv4). +The following values are displayed: + +.B totsck +.RS +Total number of sockets used by the system. +.RE + +.B tcpsck +.RS +Number of TCP sockets currently in use. +.RE + +.B udpsck +.RS +Number of UDP sockets currently in use. +.RE + +.B rawsck +.RS +Number of RAW sockets currently in use. +.RE + +.B ip-frag +.RS +Number of IP fragments currently in queue. +.RE + +.B tcp-tw +.RS +Number of TCP sockets in TIME_WAIT state. +.RE + +With the +.B SOCK6 +keyword, statistics on sockets in use are reported (IPv6). +Note that IPv6 statistics depend on +.BR sadc 's +option "-S IPV6" to be collected. +The following values are displayed: + +.B tcp6sck +.RS +Number of TCPv6 sockets currently in use. +.RE + +.B udp6sck +.RS +Number of UDPv6 sockets currently in use. +.RE + +.B raw6sck +.RS +Number of RAWv6 sockets currently in use. +.RE + +.B ip6-frag +.RS +Number of IPv6 fragments currently in use. +.RE + +With the +.B SOFT +keyword, statistics about software-based network processing are reported. +The following values are displayed: + +.B total/s +.RS +The total number of network frames processed per second. +.RE + +.B dropd/s +.RS +The total number of network frames dropped per second because there +was no room on the processing queue. +.RE + +.B squeezd/s +.RS +The number of times the softirq handler function terminated per second +because its budget was consumed or the time limit was reached, but more +work could have been done. +.RE + +.B rx_rps/s +.RS +The number of times the CPU has been woken up per second +to process packets via an inter-processor interrupt. +.RE + +.B flw_lim/s +.RS +The number of times the flow limit has been reached per second. +Flow limiting is an optional RPS feature that can be used to limit the number of +packets queued to the backlog for each flow to a certain amount. +This can help ensure that smaller flows are processed even though +much larger flows are pushing packets in. +.RE + +With the +.B TCP +keyword, statistics about TCPv4 network traffic are reported. +Note that TCPv4 statistics depend on +.BR sadc 's +option "-S SNMP" to be collected. +The following values are displayed (formal SNMP names between +square brackets): + +.B active/s +.RS +The number of times TCP connections have made a direct +transition to the SYN-SENT state from the CLOSED state per second [tcpActiveOpens]. +.RE + +.B passive/s +.RS +The number of times TCP connections have made a direct +transition to the SYN-RCVD state from the LISTEN state per second [tcpPassiveOpens]. +.RE + +.B iseg/s +.RS +The total number of segments received per second, including those +received in error [tcpInSegs]. This count includes segments received on +currently established connections. +.RE + +.B oseg/s +.RS +The total number of segments sent per second, including those on +current connections but excluding those containing only +retransmitted octets [tcpOutSegs]. +.RE + +With the +.B ETCP +keyword, statistics about TCPv4 network errors are reported. +Note that TCPv4 statistics depend on +.BR sadc 's +option "-S SNMP" to be collected. +The following values are displayed (formal SNMP names between +square brackets): + +.B atmptf/s +.RS +The number of times per second TCP connections have made a direct +transition to the CLOSED state from either the SYN-SENT +state or the SYN-RCVD state, plus the number of times per second TCP +connections have made a direct transition to the LISTEN +state from the SYN-RCVD state [tcpAttemptFails]. +.RE + +.B estres/s +.RS +The number of times per second TCP connections have made a direct +transition to the CLOSED state from either the ESTABLISHED +state or the CLOSE-WAIT state [tcpEstabResets]. +.RE + +.B retrans/s +.RS +The total number of segments retransmitted per second - that is, the +number of TCP segments transmitted containing one or more +previously transmitted octets [tcpRetransSegs]. +.RE + +.B isegerr/s +.RS +The total number of segments received in error (e.g., bad +TCP checksums) per second [tcpInErrs]. +.RE + +.B orsts/s +.RS +The number of TCP segments sent per second containing the RST flag [tcpOutRsts]. +.RE + +With the +.B UDP +keyword, statistics about UDPv4 network traffic are reported. +Note that UDPv4 statistics depend on +.BR sadc's +option "-S SNMP" to be collected. +The following values are displayed (formal SNMP names between +square brackets): + +.B idgm/s +.RS +The total number of UDP datagrams delivered per second to UDP users [udpInDatagrams]. +.RE + +.B odgm/s +.RS +The total number of UDP datagrams sent per second from this entity [udpOutDatagrams]. +.RE + +.B noport/s +.RS +The total number of received UDP datagrams per second for which there +was no application at the destination port [udpNoPorts]. +.RE + +.B idgmerr/s +.RS +The number of received UDP datagrams per second that could not be +delivered for reasons other than the lack of an application +at the destination port [udpInErrors]. +.RE + +With the +.B UDP6 +keyword, statistics about UDPv6 network traffic are reported. +Note that UDPv6 statistics depend on +.BR sadc 's +option "-S IPV6" to be collected. +The following values are displayed (formal SNMP names between +square brackets): + +.B idgm6/s +.RS +The total number of UDP datagrams delivered per second to UDP users +[udpInDatagrams]. +.RE + +.B odgm6/s +.RS +The total number of UDP datagrams sent per second from this +entity [udpOutDatagrams]. +.RE + +.B noport6/s +.RS +The total number of received UDP datagrams per second for which there +was no application at the destination port [udpNoPorts]. +.RE + +.B idgmer6/s +.RS +The number of received UDP datagrams per second that could not be +delivered for reasons other than the lack of an application +at the destination port [udpInErrors]. +.RE + +The +.B ALL +keyword is equivalent to specifying all the keywords above and therefore all the network +activities are reported. +.RE +.RE +.IP "-o [ filename ]" +Save the readings in the file in binary form. Each reading +is in a separate record. The default value of the +.I filename +parameter is the current standard system activity daily data file. +If +.I filename +is a directory instead of a plain file then it is considered as the directory +where the standard system activity daily data files are located. +The -o option is exclusive of the -f option. +All the data available from the kernel are saved in the file (in fact, +.B sar +calls its data collector +.B sadc +with the option "-S ALL". +See +.BR sadc (8) +manual page). +.IP "-P { cpu_list | ALL }" +Report per-processor statistics for the specified processor or processors. +.I cpu_list +is a list of comma-separated values or range of values (e.g., +.BR 0,2,4-7,12- ). +Note that processor 0 is the first processor, and processor +.B all +is the global average among all processors. +Specifying the +.B ALL +keyword reports statistics for each individual processor, and globally for +all processors. Offline processors are not displayed. +.IP -p +Pretty-print device names. Use this option in conjunction with option -d. +By default names are printed as +.I devM-n +where M and n are the major and minor numbers for the device. +Use of this option displays the names of the devices as they (should) appear +in /dev. Name mappings are controlled by +.IR /etc/sysconfig/sysstat.ioconf . +.IP -q +Report queue length and load averages. The following values are displayed: + +.B runq-sz +.RS +.RS +Run queue length (number of tasks waiting for run time). +.RE + +.B plist-sz +.RS +Number of tasks in the task list. +.RE + +.B ldavg-1 +.RS +System load average for the last minute. +The load average is calculated as the average number of runnable or +running tasks (R state), and the number of tasks in uninterruptible +sleep (D state) over the specified interval. +.RE + +.B ldavg-5 +.RS +System load average for the past 5 minutes. +.RE + +.B ldavg-15 +.RS +System load average for the past 15 minutes. +.RE + +.B blocked +.RS +Number of tasks currently blocked, waiting for I/O to complete. +.RE +.RE +.IP "-r [ ALL ]" +Report memory utilization statistics. The +.B ALL +keyword indicates that all the memory fields should be displayed. +The following values may be displayed: + +.B kbmemfree +.RS +.RS +Amount of free memory available in kilobytes. +.RE + +.B kbavail +.RS +Estimate of how much memory in kilobytes is available for starting new +applications, without swapping. +The estimate takes into account that the system needs some page cache to +function well, and that not all reclaimable slab will be reclaimable, +due to items being in use. The impact of those factors will vary from +system to system. +.RE + +.B kbmemused +.RS +Amount of used memory in kilobytes (calculated as total installed memory - +.B kbmemfree +- +.B kbbuffers +- +.B kbcached +- +.BR kbslab ). +.RE + +.B %memused +.RS +Percentage of used memory. +.RE + +.B kbbuffers +.RS +Amount of memory used as buffers by the kernel in kilobytes. +.RE + +.B kbcached +.RS +Amount of memory used to cache data by the kernel in kilobytes. +.RE + +.B kbcommit +.RS +Amount of memory in kilobytes needed for current workload. This is an estimate of how much +RAM/swap is needed to guarantee that there never is out of memory. +.RE + +.B %commit +.RS +Percentage of memory needed for current workload in relation to the total amount of memory (RAM+swap). +This number may be greater than 100% because the kernel usually overcommits memory. +.RE + +.B kbactive +.RS +Amount of active memory in kilobytes (memory that has been used more recently +and usually not reclaimed unless absolutely necessary). +.RE + +.B kbinact +.RS +Amount of inactive memory in kilobytes (memory which has been less recently +used. It is more eligible to be reclaimed for other purposes). +.RE + +.B kbdirty +.RS +Amount of memory in kilobytes waiting to get written back to the disk. +.RE + +.B kbanonpg +.RS +Amount of non-file backed pages in kilobytes mapped into userspace page tables. +.RE + +.B kbslab +.RS +Amount of memory in kilobytes used by the kernel to cache data structures for its own use. +.RE + +.B kbkstack +.RS +Amount of memory in kilobytes used for kernel stack space. +.RE + +.B kbpgtbl +.RS +Amount of memory in kilobytes dedicated to the lowest level of page tables. +.RE + +.B kbvmused +.RS +Amount of memory in kilobytes of used virtual address space. +.RE +.RE +.IP -S +Report swap space utilization statistics. +The following values are displayed: + +.B kbswpfree +.RS +.RS +Amount of free swap space in kilobytes. +.RE + +.B kbswpused +.RS +Amount of used swap space in kilobytes. +.RE + +.B %swpused +.RS +Percentage of used swap space. +.RE + +.B kbswpcad +.RS +Amount of cached swap memory in kilobytes. +This is memory that once was swapped out, is swapped back in +but still also is in the swap area (if memory is needed it doesn't need +to be swapped out again because it is already in the swap area. This +saves I/O). +.RE + +.B %swpcad +.RS +Percentage of cached swap memory in relation to the amount of used swap space. +.RE +.RE +.IP "-s [ hh:mm[:ss] ]" +Set the starting time of the data, causing the +.B sar +command to extract records time-tagged at, or following, the time +specified. The default starting time is 08:00:00. +Hours must be given in 24-hour format. This option can be +used only when data are read from a file (option -f). +.IP "--sadc" +Indicate which data collector is called by +.BR sar . +If the data collector is sought in PATH then enter "which sadc" to +know where it is located. +.IP -t +When reading data from a daily data file, indicate that +.B sar +should display the timestamps in the original local time of +the data file creator. Without this option, the +.B sar +command displays the timestamps in the user's locale time. +.IP "-u [ ALL ]" +Report CPU utilization. The +.B ALL +keyword indicates that all the CPU fields should be displayed. +The report may show the following fields: + +.B %user +.RS +.RS +Percentage of CPU utilization that occurred while executing at the user +level (application). Note that this field includes time spent running +virtual processors. +.RE + +.B %usr +.RS +Percentage of CPU utilization that occurred while executing at the user +level (application). Note that this field does NOT include time spent +running virtual processors. +.RE + +.B %nice +.RS +Percentage of CPU utilization that occurred while executing at the user +level with nice priority. +.RE + +.B %system +.RS +Percentage of CPU utilization that occurred while executing at the system +level (kernel). Note that this field includes time spent servicing +hardware and software interrupts. +.RE + +.B %sys +.RS +Percentage of CPU utilization that occurred while executing at the system +level (kernel). Note that this field does NOT include time spent servicing +hardware or software interrupts. +.RE + +.B %iowait +.RS +Percentage of time that the CPU or CPUs were idle during which +the system had an outstanding disk I/O request. +.RE + +.B %steal +.RS +Percentage of time spent in involuntary wait by the virtual CPU +or CPUs while the hypervisor was servicing another virtual processor. +.RE + +.B %irq +.RS +Percentage of time spent by the CPU or CPUs to service hardware interrupts. +.RE + +.B %soft +.RS +Percentage of time spent by the CPU or CPUs to service software interrupts. +.RE + +.B %guest +.RS +Percentage of time spent by the CPU or CPUs to run a virtual processor. +.RE + +.B %gnice +.RS +Percentage of time spent by the CPU or CPUs to run a niced guest. +.RE + +.B %idle +.RS +Percentage of time that the CPU or CPUs were idle and the system +did not have an outstanding disk I/O request. +.RE +.RE +.IP -V +Print version number then exit. +.IP -v +Report status of inode, file and other kernel tables. +The following values are displayed: + +.B dentunusd +.RS +.RS +Number of unused cache entries in the directory cache. +.RE + +.B file-nr +.RS +Number of file handles used by the system. +.RE + +.B inode-nr +.RS +Number of inode handlers used by the system. +.RE + +.B pty-nr +.RS +Number of pseudo-terminals used by the system. +.RE +.RE +.IP -W +Report swapping statistics. The following values are displayed: + +.B pswpin/s +.RS +.RS +Total number of swap pages the system brought in per second. +.RE + +.B pswpout/s +.RS +Total number of swap pages the system brought out per second. +.RE +.RE +.IP -w +Report task creation and system switching activity. + +.B proc/s +.RS +.RS +Total number of tasks created per second. +.RE + +.B cswch/s +.RS +Total number of context switches per second. +.RE +.RE +.IP -y +Report TTY devices activity. The following values are displayed: + +.B rcvin/s +.RS +.RS +Number of receive interrupts per second for current serial line. Serial line number +is given in the TTY column. +.RE + +.B xmtin/s +.RS +Number of transmit interrupts per second for current serial line. +.RE + +.B framerr/s +.RS +Number of frame errors per second for current serial line. +.RE + +.B prtyerr/s +.RS +Number of parity errors per second for current serial line. +.RE + +.B brk/s +.RS +Number of breaks per second for current serial line. +.RE + +.B ovrun/s +.RS +Number of overrun errors per second for current serial line. +.RE +.RE +.IP -z +Tell +.B sar +to omit output for any devices for which there was no activity during the +sample period. + +.SH ENVIRONMENT +The +.B sar +command takes into account the following environment variables: + +.IP S_COLORS +When this variable is set, display statistics in color on the terminal. +Possible values for this variable are +.IR never , +.IR always +or +.IR auto +(the latter is the default). + +Please note that the color (being red, yellow, or some other color) used to display a value +is not indicative of any kind of issue simply because of the color. It only indicates different +ranges of values. + +.IP S_COLORS_SGR +Specify the colors and other attributes used to display statistics on the terminal. +Its value is a colon-separated list of capabilities that defaults to +.BR C=33;22:H=31;1:I=32;22:M=35;1:N=34;1:R=31;22:Z=34;22 . +Supported capabilities are: + +.RS +.TP +.B C= +SGR (Select Graphic Rendition) substring for comments inserted in the binary daily +data files. + +.TP +.B H= +SGR substring for percentage values greater than or equal to 75%. + +.TP +.B I= +SGR substring for item names or values (eg. network interfaces, CPU number...) + +.TP +.B M= +SGR substring for percentage values in the range from 50% to 75%. + +.TP +.B N= +SGR substring for non-zero statistics values. + +.TP +.B R= +SGR substring for restart messages. + +.TP +.B Z= +SGR substring for zero values. +.RE + +.IP S_TIME_DEF_TIME +If this variable exists and its value is +.B UTC +then +.B sar +will save its data in UTC time (data will still be displayed in local time). +.B sar +will also use UTC time instead of local time to determine the current daily +data file located in the +.IR /var/log/sa +directory. This variable may be useful for servers with users located across +several timezones. + +.IP S_TIME_FORMAT +If this variable exists and its value is +.B ISO +then the current locale will be ignored when printing the date in the report header. +The +.B sar +command will use the ISO 8601 format (YYYY-MM-DD) instead. +The timestamp will also be compliant with ISO 8601 format. +.SH EXAMPLES +.B sar -u 2 5 +.RS +Report CPU utilization for each 2 seconds. 5 lines are displayed. +.RE + +.B sar -I 14 -o int14.file 2 10 +.RS +Report statistics on IRQ 14 for each 2 seconds. 10 lines are displayed. +Data are stored in a file called +.IR int14.file . +.RE + +.B sar -r -n DEV -f /var/log/sa/sa16 +.RS +Display memory and network statistics saved in daily data file 'sa16'. +.RE + +.B sar -A +.RS +Display all the statistics saved in current daily data file. +.SH BUGS +.I /proc +filesystem must be mounted for the +.B sar +command to work. + +All the statistics are not necessarily available, depending on the kernel version used. +.B sar +assumes that you are using at least a 2.6 kernel. +.SH FILES +.I /var/log/sa/saDD +.br +.I /var/log/sa/saYYYYMMDD +.RS +The standard system activity daily data files and their default location. +YYYY stands for the current year, MM for the current month and DD for the +current day. + +.RE +.I /proc +and +.I /sys +contain various files with system statistics. +.SH AUTHOR +Sebastien Godard (sysstat orange.fr) +.SH SEE ALSO +.BR sadc (8), +.BR sa1 (8), +.BR sa2 (8), +.BR sadf (1), +.BR sysstat (5), +.BR pidstat (1), +.BR mpstat (1), +.BR iostat (1), +.BR vmstat (8) + +.I https://github.com/sysstat/sysstat + +.I http://pagesperso-orange.fr/sebastien.godard/ diff --git a/manual/sysstat/original/man1/tapestat.1 b/manual/sysstat/original/man1/tapestat.1 new file mode 100644 index 00000000..23e93966 --- /dev/null +++ b/manual/sysstat/original/man1/tapestat.1 @@ -0,0 +1,263 @@ +.TH TAPESTAT 1 "JULY 2018" Linux "Linux User's Manual" -*- nroff -*- +.SH NAME +tapestat \- Report tape statistics. +.SH SYNOPSIS +.B tapestat [ -k | -m ] [ -t ] [ -V ] [ -y ] [ -z ] [ --human ] [ +.I interval +.B [ +.I count +.B ] ] +.SH DESCRIPTION +The +.B tapestat +command is used for monitoring the activity of tape drives connected to a system. + +The first report generated by the +.B tapestat +command provides statistics +concerning the time since the system was booted, unless the +.B -y +option is used, when this first report is omitted. +Each subsequent report +covers the time since the previous report. + +The +.I interval +parameter specifies the amount of time in seconds between +each report. +The +.I count +parameter can be specified in conjunction with the +.I interval +parameter. If the +.I count +parameter is specified, the value of +.I count +determines the number of reports generated at +.I interval +seconds apart. If the +.I interval +parameter is specified without the +.I count +parameter, the +.B tapestat +command generates reports continuously. + +.SH REPORT +The +.B tapestat +report provides statistics for each tape drive connected to the system. +The following data are displayed: + +.B r/s +.RS +The number of reads issued expressed as the number per second averaged over the interval. + +.RE +.B w/s +.RS +The number of writes issued expressed as the number per second averaged over the interval. + +.RE +.B kB_read/s | MB_read/s +.RS +The amount of data read expressed in kilobytes (by default or if option -k used) or +megabytes (if option -m used) per second averaged over the interval. + +.RE +.B kB_wrtn/s | MB_wrtn/s +.RS +The amount of data written expressed in kilobytes (by default or if option -k used) or +megabytes (if option -m used) per second averaged over the interval. + +.RE +.B %Rd +.RS +Read percentage wait - The percentage of time over the interval spent waiting for read requests +to complete. +The time is measured from when the request is dispatched to the SCSI mid-layer until it signals +that it completed. + +.RE +.B %Wr +.RS +Write percentage wait - The percentage of time over the interval spent waiting for write requests +to complete. The time is measured from when the request is dispatched to the SCSI mid-layer until +it signals that it completed. + +.RE +.B %Oa +.RS +Overall percentage wait - The percentage of time over the interval spent waiting for any +I/O request to complete (read, write, and other). + +.RE +.B Rs/s +.RS +The number of I/Os, expressed as the number per second averaged over the interval, where +a non-zero residual value was encountered. + +.RE +.B Ot/s +.RS +The number of I/Os, expressed as the number per second averaged over the interval, that +were included as "other". Other I/O includes ioctl calls made to the tape driver and +implicit operations performed by the tape driver such as rewind on close +(for tape devices that implement rewind on close). It does not include any I/O performed +using methods outside of the tape driver (e.g. via sg ioctls). +.RE +.RE +.SH OPTIONS +.IP --human +Print sizes in human readable format (e.g. 1.0k, 1.2M, etc.) +The units displayed with this option supersede any other default units (e.g. +kilobytes, sectors...) associated with the metrics. +.IP -k +Show the amount of data written or read in kilobytes per second instead of megabytes. +This option is mutually exclusive with -m. +.IP -m +Show the amount of data written or read in megabytes per second instead of kilobytes. +This option is mutually exclusive with -k. +.IP -t +Display time stamps. The time stamp format may depend +on the value of the S_TIME_FORMAT environment variable (see below). +.IP -V +Print version and exit. +.IP -y +Omit the initial statistic showing values since boot. +.IP -z +Tell +.B tapestat +to omit output for any tapes for which there was no activity +during the sample period. + +.SH CONSIDERATIONS +It is possible for a percentage value (read, write, or other) to be greater than 100 percent +(the +.B tapestat +command will never show a percentage value more than 999). +If rewinding a tape takes 40 seconds where the interval time is 5 seconds the %Oa value +would show as 0 in the intervals before the rewind completed and then show as approximately +800 percent when the rewind completes. + +Similar values will be observed for %Rd and %Wr if a tape drive stops reading or writing +and then restarts (that is it stopped streaming). In such a case you may see the r/s or w/s drop to zero and the %Rd/%Wr value could be higher than 100 when reading or writing continues +(depending on how long it takes to restart writing or reading). +This is only an issue if it happens a lot as it may cause tape wear and will impact +on the backup times. + +For fast tape drives you may see low percentage wait times. +This does not indicate an issue with the tape drive. For a slower tape drive (e.g. an older +generation DDS drive) the speed of the tape (and tape drive) is much slower than filesystem I/O, +percent wait times are likely to be higher. For faster tape drives (e.g. LTO) the percentage +wait times are likely to be lower as program writing to or reading from tape is going +to be doing a lot more filesystem I/O because of the higher throughput. + +Although tape statistics are implemented in the kernel using atomic variables they cannot be +read atomically as a group. All of the statistics values are read from different files under +/sys, because of this there may be I/O completions while reading the different files for the +one tape drive. This may result in a set of statistics for a device that contain some values +before an I/O completed and some after. + +This command uses rounding down as the rounding method when calculating per second statistics. +If, for example, you are using dd to copy one tape to another and running +.B tapestat +with an interval of 5 seconds and over the interval there were 3210 writes and 3209 reads +then w/s would show 642 and r/s 641 (641.8 rounded down to 641). In such a case if it was +a tar archive being copied (with a 10k block size) you would also see a difference between +the kB_read/s and kB_wrtn/s of 2 (one I/O 10k in size divided by the interval period of 5 +seconds). If instead there were 3210 writes and 3211 reads both w/s and r/s would both show +642 but you would still see a difference between the kB_read/s and kB_wrtn/s values of 2 kB/s. + +This command is provided with an interval in seconds. However internally the interval is +tracked per device and can potentially have an effect on the per second statistics reported. +The time each set of statistics is captured is kept with those statistics. The difference +between the current and previous time is converted to milliseconds for use in calculations. +We can look at how this can impact the statistics reported if we use an example of a tar +archive being copied between two tape drives using dd. If both devices reported 28900 kilobytes +transferred and the reading tape drive had an interval of 5001 milliseconds and the writing +tape drive 5000 milliseconds that would calculate out as 5778 kB_read/s and 5780 kB_wrtn/s. + +The impact of some retrieving statistics during an I/O completion, rounding down, and small differences in the interval period on the statistics calculated should be minimal but may be non-zero. +.SH ENVIRONMENT +The +.B tapestat +command takes into account the following environment variables: + +.IP S_COLORS +When this variable is set, display statistics in color on the terminal. +Possible values for this variable are +.IR never , +.IR always +or +.IR auto +(the latter is the default). + +Please note that the color (being red, yellow, or some other color) used to display a value +is not indicative of any kind of issue simply because of the color. It only indicates different +ranges of values. + +.IP S_COLORS_SGR +Specify the colors and other attributes used to display statistics on the terminal. +Its value is a colon-separated list of capabilities that defaults to +.BR H=31;1:I=32;22:M=35;1:N=34;1:Z=34;22 . +Supported capabilities are: + +.RS +.TP +.B H= +SGR (Select Graphic Rendition) substring for percentage values greater than or equal to 75%. + +.TP +.B I= +SGR substring for tape names. + +.TP +.B M= +SGR substring for percentage values in the range from 50% to 75%. + +.TP +.B N= +SGR substring for non-zero statistics values. + +.TP +.B Z= +SGR substring for zero values. +.RE + +.IP S_TIME_FORMAT +If this variable exists and its value is +.BR ISO +then the current locale will be ignored when printing the date in the report +header. The +.B tapestat +command will use the ISO 8601 format (YYYY-MM-DD) instead. +The timestamp displayed with option -t will also be compliant with ISO 8601 +format. + +.SH BUGS +.I /sys +filesystem must be mounted for +.B tapestat +to work. It will not work on kernels that do not have sysfs support + +This command requires kernel version 4.2 or later +(or tape statistics support backported for an earlier kernel version). + +.SH FILES +.I /sys/class/scsi_tape/st/stats/* +Statistics files for tape devices. + +.I /proc/uptime +contains system uptime. +.SH AUTHOR +Initial revision by Shane M. SEYMOUR (shane.seymour hpe.com) +.br +Modified for sysstat by Sebastien Godard (sysstat orange.fr) +.SH SEE ALSO +.BR iostat (1), +.BR mpstat (1) + +.I https://github.com/sysstat/sysstat + +.I http://pagesperso-orange.fr/sebastien.godard/ diff --git a/manual/sysstat/original/man5/sysstat.5 b/manual/sysstat/original/man5/sysstat.5 new file mode 100644 index 00000000..8e3389c0 --- /dev/null +++ b/manual/sysstat/original/man5/sysstat.5 @@ -0,0 +1,179 @@ +.TH SYSSTAT 5 "JULY 2018" Linux "Linux User's Manual" -*- nroff -*- +.SH NAME +sysstat \- sysstat configuration file. +.SH DESCRIPTION +This file is read by +.BR sa1 (8) +and +.BR sa2 (8) +shell scripts from the sysstat's set of tools. +It consists of a sequence of shell variable assignments used to +configure sysstat logging. +The variables and their meanings are: +.TP +.B COMPRESSAFTER +Number of days after which daily data files are to be compressed. +The compression program is given in the +.B ZIP +variable. + +.TP +.B HISTORY +The number of days during which a daily data file or a report +should be kept. Data files or reports older than this number of +days will be removed by the +.BR sa2 (8) +shell script. +Data files and reports are normally saved in the /var/log/sa directory, +under the name +.IR saDD +(for data files) or +.IR sarDD +(for reports), where the DD parameter indicates the current day. + +The number of files actually kept in the /var/log/sa directory may be +slightly higher than the +.B HISTORY +value due to the way the +.B sa2 +script figures +out which files are to be removed (see below "How the +.BR sa2 (8) +script applies +.B HISTORY +value"). Using a value of 28 keeps a whole month's worth of data. If +you set +.B HISTORY +to a value greater than 28 then you should consider using +.BR sadc 's +option -D to prevent older data files from being overwritten (see +.BR sadc (8) +manual page). In this latter case data files are named +.IR saYYYYMMDD +and reports +.IR sarYYYYMMDD , +where YYYY stands for the current year, MM for the +current month and DD for the current day. + +How the +.BR sa2 (8) +script applies +.B HISTORY +value + +The +.B sa2 +script uses the "find" command with the "-mtime" option to figure +out which files are to be removed. The "find" command interprets this value +as "N 24 hour periods", ignoring any fractional part. This means that the +last modified time of a given sa[r]DD data or report file, using a +.B HISTORY +of 1, has to have been modified at least two days ago before it will be +removed. And for a +.B HISTORY +of 28 that would mean 29 days ago. + +To figure out how a +.B HISTORY +of 28 is applied in practice, we need to +consider that the +.B sa2 +script that issues the "find" command to remove the +old files typically runs just before mid-night on a given system, and since +the first record from +.B sadc +can also be written to the previous day's data file +(thereby moving its modification time up a bit), the +.B sa2 +script will leave +30 files untouched. So for a setting of 28, and counting the data file of +the current day, there will always be 31 files (or 30 files, depending on the +number of days in a month) in the /var/log/sa directory during the majority +of a given day. E.g.: + +April 30th: 31 files (Apr 30th-1st, Mar 31th) +.br +May 1st: 30 files (May 1st, Apr 30th-2nd) + +Yet we can note the following exceptions (as inspected at Noon of the given +day): + +February 28th: 31 files (Feb 28th-1st, Jan 31st, 30th & 29th) +.br +March 1st: 30 files (Mar 1st, Feb 28th-2nd, Jan 31st & 30th) +.br +March 2nd: 29 files (Mar 1st & 2nd, Feb 28th-3rd, Jan. 31st) +.br +March 3rd: 28 files (Mar 1st-3rd, Feb 28th-4th) +.br +March 4th - March 28th: 28 files +.br +March 29th: 29 files +.br +March 30th: 30 files +.br +March 31st: 31 files + +(Determining the number of files in March on a leap year is left as an +exercise for the reader). + +Things are simpler if you use the sa[r]YYYYMMDD name format. +Apply the same logic as above in this case and you will find that there +are always +.B HISTORY ++ 3 files in the +.IR /var/log/sa +directory during the majority of a given day. + +.TP +.B REPORTS +Set this variable to false to prevent the +.B sa2 +script from generating reports (the +.IR sarDD +files). + +.TP +.B SA_DIR +Directory where the standard system activity daily data and report files +are saved. Its default value is +.IR /var/log/sa . + +.TP +.B SADC_OPTIONS +Options that should be passed to +.BR sadc (8). +With these options (see +.BR sadc (8) +manual page), you can select some additional data which are going to be saved in +daily data files. +These options are used only when a new data file is created. They will be +ignored with an already existing one. + +.TP +.B YESTERDAY +By default +.BR sa2 +script generates yesterday's summary, since the cron job +usually runs right after midnight. If you want +.BR sa2 +to generate the summary of the same day (for example when cron +job runs at 23:53) set this variable to no. + +.TP +.B ZIP +Program used to compress data and report files. + +.SH FILES +.IR /etc/sysconfig/sysstat + +.SH AUTHOR +Sebastien Godard (sysstat orange.fr) +.SH SEE ALSO +.BR sadc (8), +.BR sa1 (8), +.BR sa2 (8) + +.I https://github.com/sysstat/sysstat + +.I http://pagesperso-orange.fr/sebastien.godard/ diff --git a/manual/sysstat/original/man8/sa1.8 b/manual/sysstat/original/man8/sa1.8 new file mode 100644 index 00000000..9067affe --- /dev/null +++ b/manual/sysstat/original/man8/sa1.8 @@ -0,0 +1,86 @@ +.TH SA1 8 "JULY 2018" Linux "Linux User's Manual" -*- nroff -*- +.SH NAME +sa1 \- Collect and store binary data in the system activity daily data file. +.SH SYNOPSIS +.B /usr/lib64/sa/sa1 [ --boot | +.I interval +.I count +.B ] +.SH DESCRIPTION +The +.B sa1 +command is a shell procedure variant of the +.B sadc +command and handles all of the flags and parameters of that command. The +.B sa1 +command collects and stores binary data in the current standard +system activity daily data file. + +The standard system activity daily data file is named +.I saDD +unless +.BR sadc 's +option +.B -D +is used, in which case its name is +.IR saYYYYMMDD , +where YYYY stands for the current year, MM for the current month +and DD for the current day. By default it is located in the +.I /var/log/sa +directory. + +The +.I interval +and +.I count +parameters specify that the record should be written +.I count +times at +.I interval +seconds. If no arguments are given to +.B sa1 +then a single record is written. + +The +.B sa1 +command is designed to be started automatically by the cron command. + +.SH OPTIONS +.IP --boot +This option tells +.B sa1 +that the +.B sadc +command should be called without specifying the +.I interval +and +.I count +parameters in order to insert a dummy record, marking the time when the counters +restart from 0. + +.SH EXAMPLE +To collect data (including those from disks) every 10 minutes, +place the following entry in your root crontab file: + +.B 0,10,20,30,40,50 * * * * /usr/lib64/sa/sa1 1 1 -S DISK + +.SH FILES +.I /var/log/sa/saDD +.br +.I /var/log/sa/saYYYYMMDD +.RS +The standard system activity daily data files and their default location. +YYYY stands for the current year, MM for the current month and DD for the +current day. +.SH AUTHOR +Sebastien Godard (sysstat orange.fr) +.SH SEE ALSO +.BR sar (1), +.BR sadc (8), +.BR sa2 (8), +.BR sadf (1), +.BR sysstat (5) + +.I https://github.com/sysstat/sysstat + +.I http://pagesperso-orange.fr/sebastien.godard/ diff --git a/manual/sysstat/original/man8/sa2.8 b/manual/sysstat/original/man8/sa2.8 new file mode 100644 index 00000000..3a68dee2 --- /dev/null +++ b/manual/sysstat/original/man8/sa2.8 @@ -0,0 +1,72 @@ +.TH SA2 8 "JULY 2018" Linux "Linux User's Manual" -*- nroff -*- +.SH NAME +sa2 \- Create a report from the current standard system activity daily data file. +.SH SYNOPSIS +.B /usr/lib64/sa/sa2 +.SH DESCRIPTION +The +.B sa2 +command is a shell procedure variant of the +.B sar +command which writes a daily report in the +.I sarDD +or the +.I sarYYYYMMDD +file, where YYYY stands for the current year, MM for the current month +and DD for the current day. +By default the report is saved in the +.I /var/log/sa +directory. +The +.B sa2 +command will also remove reports more than one week old by default. +You can however keep reports for a longer (or a shorter) period by setting +the +.B HISTORY +environment variable. Read the +.BR sysstat (5) +manual page for details. + +The +.B sa2 +command accepts most of the flags and parameters of the +.B sar +command. + +The +.B sa2 +command is designed to be started automatically by the cron command. + +.SH EXAMPLES +To run the +.B sa2 +command daily, place the following entry in your root crontab file: + +.B 5 19 * * 1-5 /usr/lib64/sa/sa2 -A & + +This will generate by default a daily report called +.I sarDD +in the +.I /var/log/sa +directory, where the DD parameter is a number representing the day of the +month. +.SH FILES +.I /var/log/sa/sarDD +.br +.I /var/log/sa/sarYYYYMMDD +.RS +The standard system activity daily report files and their default location. +YYYY stands for the current year, MM for the current month and DD for the +current day. +.SH AUTHOR +Sebastien Godard (sysstat orange.fr) +.SH SEE ALSO +.BR sar (1), +.BR sadc (8), +.BR sa1 (8), +.BR sadf (1), +.BR sysstat (5) + +.I https://github.com/sysstat/sysstat + +.I http://pagesperso-orange.fr/sebastien.godard/ diff --git a/manual/sysstat/original/man8/sadc.8 b/manual/sysstat/original/man8/sadc.8 new file mode 100644 index 00000000..f550d2bd --- /dev/null +++ b/manual/sysstat/original/man8/sadc.8 @@ -0,0 +1,244 @@ +.TH SADC 8 "JULY 2018" Linux "Linux User's Manual" -*- nroff -*- +.SH NAME +sadc \- System activity data collector. +.SH SYNOPSIS +.B /usr/lib64/sa/sadc [ -C +.I comment +.B ] [ -D ] [ -F ] [ -L ] [ -V ] [ -S { keyword [,...] | ALL | XALL } ] [ +.I interval +.B [ +.I count +.B ] ] [ +.I outfile +.B ] +.SH DESCRIPTION +The +.B sadc +command samples system data a specified number of times +(\fIcount\fR) at a specified interval measured in seconds +(\fIinterval\fR). It writes in binary format to the specified +.I outfile +or to standard output. If +.I outfile +is set to -, then +.B sadc +uses the standard system activity daily data file (see below). +In this case, if the file already exists, +.B sadc +will overwrite it if it is from a previous month. +By default +.B sadc +collects most of the data available from the kernel. +But there are also optional metrics, for which the +relevant options must be explicitly passed to +.B sadc +to be collected (see option -S below). + +The standard system activity daily data file is named +.I saDD +unless option +.B -D +is used, in which case its name is +.IR saYYYYMMDD , +where YYYY stands for the current year, MM for the current month +and DD for the current day. +By default it is located in the +.I /var/log/sa +directory. Yet it is possible to specify an alternate location for +it: If +.I outfile +is a directory (instead of a plain file) then it will be considered +as the directory where the standard system activity daily data file +will be saved. + +When the +.I count +parameter is not specified, +.B sadc +writes its data endlessly. +When both +.I interval +and +.I count +are not specified, and option -C is not used, +a dummy record, which is used at system startup to mark +the time when the counter restarts from 0, will be written. +For example, one of the system startup script may write the restart mark to +the daily data file by the command entry: + +.B "/usr/lib64/sa/sadc -" + +The +.B sadc +command is intended to be used as a backend to the +.B sar +command. + +Note: The +.B sadc +command only reports on local activities. + +.SH OPTIONS +.IP "-C comment" +When neither the +.I interval +nor the +.I count +parameters are specified, this option tells +.B sadc +to write a dummy record containing the specified +.I comment +string. +This comment can then be displayed with option -C of +.BR sar . +.IP -D +Use +.I saYYYYMMDD +instead of +.I saDD +as the standard system activity daily data file name. +.IP -F +The creation of +.I outfile +will be forced. If the file already exists and has a format unknown to +.B sadc +then it will be truncated. This may be useful for daily data files +created by an older version of +.B sadc +and whose format is no longer compatible with current one. +.IP -L +.B sadc +will try to get an exclusive lock on the +.I outfile +before writing to it or truncating it. Failure to get the lock is fatal, +except in the case of trying to write a normal (i.e. not a dummy and not +a header) record to an existing file, in which case +.B sadc +will try again at the next interval. Usually, the only reason a lock +would fail would be if another +.B sadc +process were also writing to the file. This can happen when cron is used +to launch +.BR sadc . +If the system is under heavy load, an old +.B sadc +might still be running when cron starts a new one. Without locking, +this situation can result in a corrupted system activity file. +.IP "-S { keyword [,...] | ALL | XALL }" +Possible keywords are DISK, INT, IPV6, POWER, SNMP, XDISK, ALL, and XALL. + +Specify which optional activities should be collected by +.BR sadc . +Some activities are optional to prevent data files from growing too large. +The +.B DISK +keyword indicates that +.B sadc +should collect data for block devices. +The +.B INT +keyword indicates that +.B sadc +should collect data for system interrupts. +The +.B IPV6 +keyword indicates that IPv6 statistics should be +collected by +.BR sadc . +The +.B POWER +keyword indicates that +.B sadc +should collect power management statistics. +The +.B SNMP +keyword indicates that SNMP statistics should be +collected by +.BR sadc . +The +.B ALL +keyword is equivalent to specifying all the keywords above and therefore +all previous activities are collected. + +The +.B XDISK +keyword is an extension to the +.B DISK +one and indicates that partitions and filesystems statistics should be collected by +.B sadc +in addition to disk statistics. This option works only with kernels 2.6.25 +and later. +The +.B XALL +keyword is equivalent to specifying all the keywords above (including +keyword extensions) and therefore all possible activities are collected. + +Important note: The activities (including optional ones) saved in an existing +data file prevail over those selected with option -S. +As a consequence, appending data to an existing data file will result in +option -S being ignored. +.IP -V +Print version number then exit. + +.SH ENVIRONMENT +The +.B sadc +command takes into account the following environment variable: + +.IP S_TIME_DEF_TIME +If this variable exists and its value is +.BR UTC +then +.B sadc +will save its data in UTC time. +.B sadc +will also use UTC time instead of local time to determine the current +daily data file located in the +.IR /var/log/sa +directory. +.SH EXAMPLES +.B /usr/lib64/sa/sadc 1 10 /tmp/datafile +.RS +Write 10 records of one second intervals to the /tmp/datafile binary file. +.RE + +.B /usr/lib64/sa/sadc -C Backup_Start /tmp/datafile +.RS +Insert the comment Backup_Start into the file /tmp/datafile. +.RE +.SH BUGS +The +.I /proc +filesystem must be mounted for the +.B sadc +command to work. + +All the statistics are not necessarily available, depending on the kernel version used. +.B sadc +assumes that you are using at least a 2.6 kernel. +.SH FILES +.I /var/log/sa/saDD +.br +.I /var/log/sa/saYYYYMMDD +.RS +The standard system activity daily data files and their default location. +YYYY stands for the current year, MM for the current month and DD for the +current day. + +.RE +.I /proc +and +.I /sys +contain various files with system statistics. +.SH AUTHOR +Sebastien Godard (sysstat orange.fr) +.SH SEE ALSO +.BR sar (1), +.BR sa1 (8), +.BR sa2 (8), +.BR sadf (1), +.BR sysstat (5) + +.I https://github.com/sysstat/sysstat + +.I http://pagesperso-orange.fr/sebastien.godard/ diff --git a/manual/sysstat/original/sysstat-12.0.5.lsm b/manual/sysstat/original/sysstat-12.0.5.lsm new file mode 100644 index 00000000..41dd3d93 --- /dev/null +++ b/manual/sysstat/original/sysstat-12.0.5.lsm @@ -0,0 +1,35 @@ +Begin4 +Title: sysstat - the sar, sadf, mpstat, iostat, tapestat, pidstat and cifsiostat commands for Linux +Version: 12.0.5 +Entered-date: 2019-05-31 +Description: The sysstat package contains the sar, sadf, mpstat, iostat, tapestat, + pidstat, cifsiostat and sa tools for Linux. + The sar command collects and reports system activity + information. + The information collected by sar can be saved in a file + in a binary format for future inspection. + The statistics reported by sar concern I/O transfer rates, + paging activity, process-related activities, interrupts, + network activity, memory and swap space utilization, CPU + utilization, kernel activities and TTY statistics, among + others. Both UP and SMP machines are fully supported. + The sadf command is used to display data collected by sar in various + formats (XML, database-friendly, etc.) and to draw graphs (SVG). + The mpstat command reports global and per-processor statistics. + The iostat command reports CPU utilization and I/O statistics + for disks. + The tapestat command reports statistics for tape drives connected + to the system. + The pidstat command reports statistics for Linux tasks (processes). + The cifsiostat command reports I/O statistics for CIFS filesystems. + NB: Send bugs, patches, suggestions and/or questions to + (sysstat [at] orange.fr). + URL: http://pagesperso-orange.fr/sebastien.godard/ +Keywords: system administration, system monitoring, sar, sadf, iostat, mpstat, tapestat, pidstat, system accounting, performance, tuning +Author: sysstat@NOSPAM.orange.fr (Sebastien Godard) +Maintained-by: sysstat@NOSPAM.orange.fr (Sebastien Godard) +Primary-site: http://pagesperso-orange.fr/sebastien.godard/ + 536kiB sysstat-12.0.5.tar.xz +Alternate-site: +Copying-policy: GPL +End diff --git a/manual/sysstat/translation_list b/manual/sysstat/translation_list new file mode 100644 index 00000000..770cd633 --- /dev/null +++ b/manual/sysstat/translation_list @@ -0,0 +1,11 @@ +●:sysstat:12.0.5:2018/07/01:cifsiostat:1:2019/07/07::ysato444@ybb.ne.jp:Yuichi SATO: +●:sysstat:12.0.5:2018/07/01:iostat:1:2019/07/06::ysato444@ybb.ne.jp:Yuichi SATO: +●:sysstat:12.0.5:2018/07/01:mpstat:1:2019/07/06::ysato444@ybb.ne.jp:Yuichi SATO: +●:sysstat:12.0.5:2018/07/01:pidstat:1:2019/07/07::ysato444@ybb.ne.jp:Yuichi SATO: +●:sysstat:12.0.5:2018/07/01:sadf:1:2019/07/08::ysato444@ybb.ne.jp:Yuichi SATO: +●:sysstat:12.0.5:2019/04/01:sar:1:2019/07/06::ysato444@ybb.ne.jp:Yuichi SATO: +×:sysstat:12.0.5:2018/07/01:tapestat:1::::: +●:sysstat:12.0.5:2018/07/01:sysstat:5:2019/07/09::ysato444@ybb.ne.jp:Yuichi SATO: +●:sysstat:12.0.5:2018/07/01:sa1:8:2019/07/09::ysato444@ybb.ne.jp:Yuichi SATO: +●:sysstat:12.0.5:2018/07/01:sa2:8:2019/07/09::ysato444@ybb.ne.jp:Yuichi SATO: +●:sysstat:12.0.5:2018/07/01:sadc:8:2019/07/09::ysato444@ybb.ne.jp:Yuichi SATO: -- 2.11.0