--- FAQ
+++ FAQ
@@ -406,9 +406,9 @@
Nor do you have to be concerned about using up all your disk space.
sar will use a few hundred kilobytes for a whole day's worth of data, and it
normally only stores one week worth (this can be configured via the HISTORY
-variable in the /etc/sysconfig/sysstat file). It is entirely self limiting.
+variable in the /etc/sysstat/sysstat file). It is entirely self limiting.
Moreover, you can ask sar to compress its datafiles older than a certain
-number of days: see the COMPRESSAFTER parameter in the /etc/sysconfig/sysstat
+number of days: see the COMPRESSAFTER parameter in the /etc/sysstat/sysstat
configuration file.
~~~
@@ -448,7 +448,7 @@
By default sar saves its data in the standard system activity data file,
the /var/log/sa/sa
file, where is the current day in the month.
To prevent sar from overwriting any existing files, just set the variable
-HISTORY in /etc/sysconfig/sysstat to the number of days during which data
+HISTORY in /etc/sysstat/sysstat to the number of days during which data
must be kept. When this variable has a value greater than 28, sa1 script
uses a month-by-month directory structure; datafiles are named YYYYMM/saDD
and the script maintains links to these datafiles to mimic the standard
--- README
+++ README
@@ -83,8 +83,8 @@
${PREFIX}/share/doc/sysstat-x.y.z/*
/var/log/sa
${INIT_DIR}/sysstat
-/etc/sysconfig/sysstat
-/etc/sysconfig/sysstat.ioconf
+/etc/sysstat/sysstat
+/etc/sysstat/sysstat.ioconf
/etc/cron.d/sysstat
/etc/rc.d/rc.sysstat for [SLACKWARE]
${RC_DIR}/rc2.d/S03sysstat