Description of problem:
yum-cron runs at nice 10 (from anacrontab), restarted service inherit that priority.
# Reset our priority so restarted services don't inherit the lower priority
# from cron
renice 0 $$
To the 0yum.cron script should fix.
Version-Release number of selected component (if applicable):
Looks like you would want:
renice 0 $$ > /dev/null
to avoid the output from renice.
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
yum-updatesd suffers from the same issue (at nice +19 instead of nice +10), see Bug 552279 for details and a workaround.
packagekit-cron is probably the last option for doing automatic updates on a
standalone RHEL6 system. I haven't tested it to see whether it suffers from a
similar bug, but it's a more ambitious framework than either yum-updatesd or
yum-cron so it might address the issue.
Alternately one would have to look at satellite or spacewalk, which are pretty
heavyweight solutions generally targeted toward large shops.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
The anacron scheduler starts the yum-cron utility with the "nice" value of 10. This caused Yum's RPM transactions to run at very low priority level. Also, any updated service inherited this "nice" value, which influenced the system behavior. This update adds the "reset_nice" configuration option, which allows Yum to reset the "nice" value to 0 before running an RPM transaction. With this option set, Yum's RPM transactions run at normal priority level so that updated services are restarted with normal priority as expected.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.