Bug 34473
Summary: | sa1 in adm crontab cannot write to /var/log/sa root | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <borro04> |
Component: | sysstat | Assignee: | Preston Brown <pbrown> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-04-03 11:49:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2001-04-03 11:49:00 UTC
sa1 and sa2 are already run in /etc/cron.hourly/sysstat and /etc/cron.daily/sysstat respectively. They are run as root, not adm, so there is no problem. So I should not schedule sa1 or sa2 in adm's crontab. Is this how Red Hat intends for sar to be run, only by root? I will look at sysstat-3.2.4 to see if this changed. I was unable to get sa03 or sa02 file for today or yesterday with sysstat-3.2.4. I also have not discovered all the proper uses for this revision. This has drastically different than the way I have used sar on any platform. Now I don't have to deal with crontab anymore. Sar just works. Thanks for the comments. |