From eb2cf83a5e40d0159357d637feffc35446562edf Mon Sep 17 00:00:00 2001 From: Manuel Canales Esparcia Date: Sat, 7 May 2005 10:41:02 +0000 Subject: [PATCH] Tagged sysstat.xml git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@4004 af4574ff-66df-0310-9fd7-8a98e5e911e0 --- general/sysutils/sysstat.xml | 332 +++++++++++++++++++---------------- 1 file changed, 179 insertions(+), 153 deletions(-) diff --git a/general/sysutils/sysstat.xml b/general/sysutils/sysstat.xml index 9f5e6db482..36e3bf89fc 100644 --- a/general/sysutils/sysstat.xml +++ b/general/sysutils/sysstat.xml @@ -13,98 +13,107 @@ ]> - -$LastChangedBy$ -$Date$ - - -Sysstat-&sysstat-version; - -Sysstat + - -Introduction to <application>Sysstat</application> + + $LastChangedBy$ + $Date$ + -The Sysstat package contains utilities to -monitor system performance and usage activity. -Sysstat contains the sar utility, -common to many commercial Unixes, and tools you can schedule via cron to -collect and historize performance and activity data. + Sysstat-&sysstat-version; -Package information - -Download (HTTP): - -Download (FTP): - -Download MD5 sum: -&sysstat-md5sum; -Download size: -&sysstat-size; -Estimated disk space required: -&sysstat-buildsize; -Estimated build time: -&sysstat-time; - + + Sysstat + -<application>Sysstat</application> dependencies -Recommended - - + + Introduction to Sysstat - + The Sysstat package contains utilities + to monitor system performance and usage activity. + Sysstat contains the sar + utility, common to many commercial Unixes, and tools you can schedule via + cron to collect and historize performance and activity data. - -Installation of <application>Sysstat</application> + Package Information + + + Download (HTTP): + + + Download (FTP): + + + Download MD5 sum: &sysstat-md5sum; + + + Download size: &sysstat-size; + + + Estimated disk space required: &sysstat-buildsize; + + + Estimated build time: &sysstat-time; + + -Install Sysstat by running the -following commands: + Sysstat Dependencies -make config && -make + Recommended + -Now, as the root user: + -make install + + Installation of Sysstat - + Install Sysstat by running the + following commands: - -Command explanations +make config && +make -make config: Runs the interactive configuration -process. The first question prompts you for an -Installation directory. Reply -with /usr, as -this is equivalent to Autoconf's ---prefix=/usr parameter to -configure. For all other prompts, you may -press Enter to accept the (very sane) defaults. When -prompted for Number of daily data files to keep: -[7], you may wish to keep a larger number of files. -However, don't exceed 25 because Sysstat will -resuse existing files the next month, leading to erroneous daily -reports. + Now, as the root user: - +make install - -Configuring <application>Sysstat</application> + -Cron information + + Command Explanations -To begin gathering Sysstat history -information, you must add to, or create a privileged user's crontab. The -default history data location is -/var/log/sa. The user running -Sysstat utilities via cron must have write -access to this location. + make config: Runs the interactive configuration + process. The first question prompts you for an + Installation directory. + Reply with /usr, as this is equivalent to + Autoconf's parameter + to configure. For all other prompts, you may + press Enter to accept the (very sane) defaults. When + prompted for Number of daily data files to keep: + [7], you may wish to keep a larger number of files. + However, don't exceed 25 because Sysstat will + resuse existing files the next month, leading to erroneous daily reports. -Below is an example of what to install in the crontab. Adjust the -parameters to suit your needs. Use man sa1 and -man sa2 for information about the commands. + -# 8am-7pm activity reports every 10 minutes during weekdays + + Configuring Sysstat + + + Cron Information + + To begin gathering Sysstat history + information, you must add to, or create a privileged user's crontab. The + default history data location is + /var/log/sa. The user running + Sysstat utilities via cron must have write + access to this location. + + Below is an example of what to install in the crontab. Adjust the + parameters to suit your needs. Use man sa1 and + man sa2 for information about the commands. + +# 8am-7pm activity reports every 10 minutes during weekdays 0 8-18 * * 1-5 /usr/lib/sa/sa1 600 6 & # 7pm-8am activity reports every hour during weekdays @@ -114,101 +123,118 @@ parameters to suit your needs. Use man sa1 and 0 * * * 0,6 /usr/lib/sa/sa1 & # Daily summary prepared at 19:05 -5 19 * * * /usr/lib/sa/sa2 -A & +5 19 * * * /usr/lib/sa/sa2 -A & -Ensure you submit the revised crontab to the cron daemon. - + Ensure you submit the revised crontab to the cron daemon. -System startup information - -sysstat + -At system startup, a LINUX RESTART message must be inserted in the daily -data file to reinitialize the kernel counters. This can be automated by -installing the /etc/rc.d/init.d/sysstat init script -included in the package using -the following command: + + System Startup Information -make install-sysstat - + + sysstat + - + At system startup, a LINUX RESTART message must be inserted in the daily + data file to reinitialize the kernel counters. This can be automated by + installing the /etc/rc.d/init.d/sysstat init script + included in the package using + the following command: - -Contents +make install-sysstat - -Installed Programs -Installed Libraries -Installed Directories + - -iostat, mpstat, sar, sa1, sa2 and sadc -None -/usr/lib/sa and /var/log/sa - - + - -Short Descriptions - + + Contents - -iostat -reports CPU statistics and input/output -statistics for devices and partitions. - -iostat - - + + Installed Programs + Installed Libraries + Installed Directories - -mpstat -reports individual or combined processor related -statistics. - -mpstat - - + + iostat, mpstat, sar, sa1, sa2, and sadc + None + /usr/lib/sa and /var/log/sa + + - -sar - collects, reports and saves system activity -information. - -sar - - + + Short Descriptions + + - -sa1 -collects and stores binary data in the system activity daily -data file. It is a front end to sadc designed to be run -from cron. - -sa1 - - + + iostat + + reports CPU statistics and input/output + statistics for devices and partitions. + + iostat + + + - -sa2 -writes a summarized daily activity report. It is a front end -to sar designed to be run from cron. - -sa2 - - + + mpstat + + reports individual or combined processor related statistics. + + mpstat + + + - -sadc -is the system activity data collector, used as a backend for -sar. - -sadc - - - + + sar + + collects, reports and saves system activity information. + + sar + + + - + + sa1 + + collects and stores binary data in the system activity daily + data file. It is a front end to sadc designed to be run + from cron. + + sa1 + + + + + + sa2 + + writes a summarized daily activity report. It is a front end + to sar designed to be run from cron. + + sa2 + + + + + + sadc + + is the system activity data collector, used as a backend for + sar. + + sadc + + + + + + +