File sysstat-8.0.4-sysconfdir.diff of Package sysstat

--- sysstat-11.0.0/FAQ	2014-06-08 10:28:50.000000000 -0400
+++ FAQ	2014-07-17 22:13:10.841736018 -0400
@@ -430,9 +430,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.
 
 ~~~
@@ -472,7 +472,7 @@
 By default sar saves its data in the standard system activity data file,
 the /var/log/sa/saDD file, where DD 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
--- sysstat-11.0.0/README	2014-03-02 09:05:23.000000000 -0500
+++ README	2014-07-17 22:14:50.977729171 -0400
@@ -86,8 +86,8 @@
 /lib/systemd/system/sysstat-collect.timer	if OS uses systemd
 /lib/systemd/system/sysstat-summary.service	if OS uses systemd
 /lib/systemd/system/sysstat-summary.timer	if OS uses systemd
-/etc/sysconfig/sysstat
-/etc/sysconfig/sysstat.ioconf
+/etc/sysstat/sysstat
+/etc/sysstat/sysstat.ioconf
 /etc/cron.d/sysstat
 /etc/rc.d/rc.sysstat			(depending on your distro)
 ${RC_DIR}/rc2.d/S03sysstat