[rhn-users] RHN problem with noticing machines that are out of date?

[inode0]

I have an account that only has three registered physical systems (+5
guests). All three physical systems are running RHEL5. Yesterday a
bunch of errata were released and I received mail telling me my
notebook, which hasn't been turned on since prior to the release of
those errata, is out of date this morning. One of the other machines
which is on 24x7 I updated myself and the remaining machine, which is
out of date, showed up as still up to date on RHN this morning. I ran
rhn-profile-sync on that one and RHN woke up and noticed it was out of
date too. However, yum-updatesd doesn't ever seem to notice or do
anything.

I'm very confused about what is the expected behavior. I guess I
expect that the day after errata are released RHN will have a three
machine account in order without user intervention.

And I'm very curious why this isn't something that lots of people are
having to cope with unless everyone has given up and just run up2date
from cron rather than relying on the web interface to just work?!

John