#9439 NORM Not Tri: Sync RTC clock to OATS server from initrd

[Zarro Boogs per Child]

#9439: Sync RTC clock to OATS server from initrd
---------------------------------------+------------------------------------
           Reporter:  martin.langhoff  |       Owner:  martin.langhoff
               Type:  enhancement      |      Status:  new            
           Priority:  normal           |   Milestone:  Not Triaged    
          Component:  initramfs        |     Version:  not specified  
         Resolution:                   |    Keywords:  ml8.2.3        
        Next_action:  never set        |    Verified:  0              
Deployment_affected:                   |   Blockedby:                 
           Blocking:                   |  
---------------------------------------+------------------------------------

Comment(by martin.langhoff):

 This of course deals with the 'clock is in a bad state, or too far
 forward' case.

 The "clock is far back in time", "everlasting lease" is handled with
 related changes in olpc-update-query. See

 http://dev.laptop.org/git/projects/olpc-
 update/commit/?id=b5db2c889ef08242c62bddbb7bd56a325a0e22c5
 http://dev.laptop.org/git/projects/olpc-
 update/commit/?id=3468006f75f55428a37abe8d853df84253157b40

 In both cases, we only sync with the server time if the time delta is
 large -- small offsets are not an issue wrt antitheft, and better dealt
 with by ntpd. And wesure don't want to confuse a running ntpd.

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