#4638 NORM Never A: Journal date/times are sometimes out of date.

[Zarro Boogs per Child]

#4638: Journal date/times are sometimes out of date.
-------------------------------+--------------------------------------------
  Reporter:  MitchellNCharity  |       Owner:  tomeu         
      Type:  defect            |      Status:  new           
  Priority:  normal            |   Milestone:  Never Assigned
 Component:  journal-activity  |     Version:                
Resolution:                    |    Keywords:  update.1?     
  Verified:  0                 |  
-------------------------------+--------------------------------------------

Comment(by gnu):

 Once we get real suspend-on-idle, I have a blue-sky thought about how to
 make things that should run when we aren't suspended, but shouldn't wake
 us from suspend.  You could have a thread that awakens once a minute (when
 the journal is in view, and the screen isn't closed or screensaved) and
 tells the main thread to update the times.  Q is how to tell the kernel
 that we don't care about running that when we're suspended for power
 consumption.  My suggestion is to run it at a very low "nice" value.  The
 kernel could decline to wake up for any timer set by a process with nice <
 15.

 Even if it does wake up, it only wakes once a minute; and the messages can
 probably be reworded so that this can be slowed to every 5 minutes, or
 every 24 hours, after sufficient time has passed.  E.g. "Half an hour ago"
 is fine when it's really 32 minutes ago; "Yesterday after 4PM" is fine
 when it was 4:33.

 Of course, these relative times were put in because we didn't know the
 correct time & timezone.  (See bugs #2684, #4155, #4157, #2896).  We're
 fixing that, so we could just make them absolute times again, then they'd
 only need updating when we moved into a different timezone :-).  We'd
 avoid the whole wakeup and staleness issue.

-- 
Ticket URL: <http://dev.laptop.org/ticket/4638#comment:10>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system