--- In [email protected], "Soyuz" <[EMAIL PROTECTED]> wrote: > > No other OS. > > Once I fix the time, it seems like time is Ok till next reboot. > > Not suspecting the BIOS battery at this stage as these days its not > common for them to drain before 5 yrs. But will give it a check. > >
Annoyingly enough my clock issue is gone without any required fixing. Rebooted and observed the BIOS time in various interval to see if it's the battery that causing it. It wasn't. And now it's been few hours and seems like clock in going by clock. :P No time deviation in my desktop clock applet. Arghhh!!! Now I will have to keep wondering what lies beneath and when it may surface again. But it was indeed interesting to learn that OSes like Linux, Win (maybe Mac too) maintain their own clock in kernel while running (boot, read from BIOS and start ticking own clock using timer interrupt). During shutdown they may set the time back to BIOS. Hmm... it may seem very strange design choice (not reading/getting the time whenever needed directly from bios) but it makes sense for reasons that I am not going to bore everybody with. Checkout http://tldp.org/HOWTO/Clock-2.html and ofcourse googling with give out more. > > > > On Nov 5, 2007 7:15 AM, Soyuz <mahafuz_bdc@> wrote: > > > > > > > > Anybody has experience with Linux system clock gaining/losing time or > > > behaving crazy. > > > > > > It seems like my clock goes random with every boot of my laptop > > > (ppenSUSE 10.3, Dell Inspiron 6400). > > > > > > System is set to interpret CMOS clock as localtime and timezone is set > > > to proper (EST for melbourne). > > > > > > Btw, for curiosity, any of you in server environment, did you face the > > > clock issue with Windows servers (long uptime)? > > > > > > Regards, > > > > > > Soyuz > > > > > > > > > > > > > > > [Non-text portions of this message have been removed] > > >
