Bug 34873 - difference between sysstat version RH7.0 and Linux
Summary: difference between sysstat version RH7.0 and Linux
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sysstat
Version: 7.0
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Preston Brown
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-04-05 11:26 UTC by Need Real Name
Modified: 2007-04-18 16:32 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-04-05 15:13:05 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2001-04-05 11:26:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT; Computer 
Associates International v1.16; Computer Associates International v1.52)


How can I tell the difference between sysstat distributed by RedHat and 
the original developer's versions?
Could I install a version of sysstat not listed on RedHat's websit?
If I would loose RedHat support by installing another sysstat package, how 
can I tell if RedHat supports a specific version?
Should I only get the package off the CD or from the RH website?

Reproducible: Always
Steps to Reproduce:
Just a question of determining which sysstat is supported.


	

Actual Results:  Confusion.

Expected Results:  get sar to work

Comment 1 Need Real Name 2001-04-05 15:13:00 UTC
Can sysstat-3.3.3-1 distributed from RedHat 7.0 be installed and supported on 
RedHat 6.2?
Or would it be better to use the Linux general sysstat package?

If there is a better place to ask questions on sysstat support on RedHat, 
let me know.

Comment 2 Preston Brown 2001-04-07 15:46:57 UTC
We don't officially support running packages from newer releases on older 
versions of Red Hat Linux, unless we have made an official update (available 
ftom updates.redhat.com or Red Hat Network).  So for 6.2, you can either 
recompile/use the 7.0 packages, or the maintainer's version of the packages, 
your choice.  In either case, we don't officially support this on 6.2.

That isn't to say it won't work.



Note You need to log in before you can comment on or make changes to this bug.