Re: [Cooker] Clock configuration settings on 2008.1

[Steve Morris]

Adam Williamson wrote:
> On Sat, 2008-05-31 at 09:02 +1000, Steve Morris wrote:
>   
> > Can anybody tell me where to find the config file containing the clock 
> > setting specifications in 2008.1. On my new Acer laptop the date and 
> > time every time I boot is wrong even though the Bios is correct. I need 
> > to check whether Mandriva for some reason thinks that the Bios is 
> > configured for UTC time, either that or there is a bug in Mandriva where 
> > it cannot properly handle a locale of Australia and a Bios date in 
> > American format. Thankyou.
> >     
>
> It's a known bug with a known workaround (that should've been fixed
> already...) - https://qa.mandriva.com/show_bug.cgi?id=36522
>   
Thanks Adam. I checked out the bug entry, and checked the files on my 
laptop and they were both(/etc/sysconfig/clock and /etc/adjtime) set 
correctly to reflect local time. The subtle difference I had was that 
yesterday (30/05/2008), when I booted the laptop on the train to work, 
when I booted on the train on the way home, and when I booted at home 
the Mandriva time was set to 04:00 AM 31/05/2008 on each occasion even 
though each time I corrected the time through the tray clock applet. At 
home I also checked the Bios time just to make sure it wasn't an issue, 
and found that it had been decremented by 1 hour. I adjusted both times 
to the correct local time.
With the boot I mentioned above to check the files, I checked the clock 
and it was correctly set at 09:45AM 31/05/2008 in both Mandriva and the 
Bios, so I am a little confused at the moment. I do not have syncing 
with an NTP server active as the laptop is hardly ever connected to the 
internet. The only time it is ever connected to the internet is when I 
do a urpmi --auto-update, and on those occasions it is connected behind 
a firewall, which I suspect would be blocking the NTP requests anyway, 
plus the organisation is moving to firewalls that don't allow Mandriva 
(Linux?) to talk to them at the moment.
Clutching at straws, I will have to monitor the clock issue to see if it 
reoccurs, and whether or not it is an end of the month issue, or even 
whether or not there is an issue on the 30th day of a 31 day month. I 
have seen these sorts of clock issues in an operating 
system/applications before, so I am keeping an open mind.

regards,
Steve

begin:vcard
fn:Steve Morris
n:Morris;Steve
email;internet:samorris@netspace.net.au
x-mozilla-html:TRUE
version:2.1
end:vcard