<div dir="ltr"><div>I scheduled a jobs on the morning of the 17th December to execute the following morning at 9AM, it seems that although the rhnsd interval is set to 240 [1] the job was not picked up and executed until approx 28 hours after I created the schedule. </div><div>[1] # cat /etc/sysconfig/rhn/rhnsd INTERVAL=240 </div><div> </div> Summary: Package Install scheduled by swadmin Details: This action will be executed after 12/18/14 9:00:00 AM GMT This action's status is: Completed. The client picked up this action on 12/18/14 3:03 PM The client completed this action on 12/18/14 3:05 PM Client execution returned "Update Succeeded" (code 0) Packages Scheduled: nss-util-3.16.2.3-2.el6_6.x86_64 rpm-python-4.8.0-38.el6_6.x86_64 rpm-4.8.0-38.el6_6.x86_64 system-config-firewall-base-1.2.27-7.2.el6_6.noarch selinux-policy-3.7.19-260.el6_6.1.noarch nss-3.16.2.3-3.el6_6.x86_64 nss-sysinit-3.16.2.3-3.el6_6.x86_64 rpm-build-4.8.0-38.el6_6.x86_64 nss-tools-3.16.2.3-3.el6_6.x86_64 ruby-1.8.7.374-3.el6_6.x86_64 ruby-libs-1.8.7.374-3.el6_6.x86_64 rpm-libs-4.8.0-38.el6_6.x86_64 selinux-policy-targeted-3.7.19-260.el6_6.1.noarch Time: 12/18/14 9:00:00 AM GMT Also, this job was pard of an action chain to reboot the system when the package update was complete (not necessary but I wanted to test it) this was not completed until 4-5 hours after the package update which would have only taken a few minutes. I'm surprised that this didn't happen immediately afterward. Summary: System reboot scheduled by mattb Details: This action will be executed after 12/18/14 9:00:00 AM GMT This action's status is: Completed. The client picked up this action on 12/18/14 3:05 PM The client completed this action on 12/18/14 7:48 PM Client execution returned "null" (code null) Time: 12/18/14 9:00:00 AM GMT Am I misunderstanding how the scheduler works? I won't be able to rely on this in production if I can't predict with some accuracy when the jobs will execute. Regards, </div>