Merge lp://staging/~kirkland/update-manager/522452 into lp://staging/update-manager

Weird, I was just looking at this issue today. I also think doing this as a cron job would improve things noticeably for the user.

The one corner case vorlon pointed out would be laptop users who might not leave their system on routinely.

On Thu, Feb 25, 2010 at 8:41 PM, Bryce Harrington
<email address hidden> wrote:
> Weird, I was just looking at this issue today.  I also think doing this as a cron job would improve things noticeably for the user.

Heh, well, I'd like to get mvo's opinion, but I like my solution.

> The one corner case vorlon pointed out would be laptop users who might not leave their system on routinely.

True. I thought of this too. Which is why I moved the stamp from
/var/run to /var/lib. At least that way, it would be somewhat more
persistent. Not a total solution, but at least better.

Furthermore, update-motd isn't *really* targeted at laptop users.
They (usually) have a desktop environment and thus all sorts of popups
and notifications.

Thanks for nudging this along, Bryce.

Aha!

I have a much better way of doing this, Bryce :-)

No need for a cronjob.

In the update motd script:
  if upgrade-available cache file is populated, print it
  else if it's available but empty, check its timestamp, and if it's older than 1 day old, update the cache file in the background
  else if it doesn't exist, update it in the background

Profit! I'm going to go ahead and commit that version now.