#9705 NORM Not Tri: os42 - /etc/adjtime not set up

[Zarro Boogs per Child]

#9705: os42 - /etc/adjtime not set up
------------------------------------+---------------------------------------
           Reporter:  mikus         |       Owner:                                   
               Type:  defect        |      Status:  closed                           
           Priority:  normal        |   Milestone:  Not Triaged                      
          Component:  not assigned  |     Version:  Development build as of this date
         Resolution:  fixed         |    Keywords:                                   
        Next_action:  no action     |    Verified:  0                                
Deployment_affected:                |   Blockedby:                                   
           Blocking:                |  
------------------------------------+---------------------------------------
Changes (by Quozl):

  * next_action:  never set => no action


Comment:

 Replying to [comment:3 mikus]:
 > I was not asking about being disk backed.  On os40 (and I believe os41),
 after a reboot /etc/adjtime would contain numbers.  On os42, adjtime
 appears to be reset to all zeros on every boot.  This is a regression, and
 ought to be fixed.

 We know you were not asking about being disk backed, but it is the lack of
 disk backing for the file that causes it to not contain any numbers after
 boot.  Because the file is seen to be empty, the boot scripts create it
 with zeros each time.  It is not a regression, it is intentional, and I
 don't think it should be changed.

 > The reason I picked up on this is that I saw in a discussion (I forget
 where) that since the OLPC internally uses GMT, the third line in
 /etc/adjtime ought to say 'UTC'.  I've been checking to see if it says
 'LOCAL' - if so, I manually change that third line to say 'UTC'.

 How nice of you.  But it is not necessary.

 The hardware clock uses UTC, not GMT.

 UTC is assumed when the file is all zeroes.  You can see this if you type,
 as root:

 {{{
 rtcwake --mode mem --seconds 10
 }}}

 rtcwake emits "assuming RTC uses UTC"

 If you are aware of any application or utility that misinterprets the zero
 values as not being UTC, let me know.

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