Bug 450958
Summary: | queuing a check via dbus should reset the run_interval timer | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | James Ralston <ralston> |
Component: | yum | Assignee: | James Antill <james.antill> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.2 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-06-11 22:03:03 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
James Ralston
2008-06-11 21:39:31 UTC
yum-updatesd isn't designed to be used that way to do what you want. What you probably want is to _not_ run the yum-updatesd service, but to just call "/usr/sbin/yum-updatesd --oneshot" from your cron script. And/or install yum-cron from epel. The whole point of the run_interval code is to try and make the yum-updatesd's run at different times. For instance if 90%+ of people log onto their machines between 8:55 and 9:05, triggering a check update in some way, we don't want all of their yum-updatesd's to syncronize within that 10 minute window. Ah; --oneshot wasn't mentioned in the (stub) man page for yum-updatesd. Yes, that's definitely want I want here. Suggestion: consider documenting --oneshot in the yum-updatesd(8) man page... |