Red Hat Bugzilla – Bug 34473
sa1 in adm crontab cannot write to /var/log/sa root
Last modified: 2007-04-18 12:32:31 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT; Computer
Associates International v1.16; Computer Associates International v1.52)
adm crontab contains /usr/lib/sa/sa1 and /usr/lib/sa/sa2
/var/log/sa owned by root, the adm user cannot write its crontab
information to /var/log/sa
Steps to Reproduce:
1.add sa1 and sa2 to 'adm' crontab
2.schedule sa1 to run every 5 minutes
3.check /var/log/sa, not files created
Actual Results: no file created by sa1
mail output Cannot open /var/log/sa/sa07: Permission denied
Expected Results: /var/log/sa/sa07 or the current date should exist
but it cannot because by default, /var/log/sa is owned by root
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.