[email protected] wrote: > Hi, > > On Tue, 29 Mar 2005 15:07:28 +0200 > Antonio Coralles <[EMAIL PROTECTED] <mailto:>> wrote: > >> >> I've a strange problem: The clock of my computer ticks to fast - > i get >> >> an error of about 30 minutes per day ... >> >> This problem just occured recently - a few days ago everthing was ok, >> >> possibly before 'emerge -up --deep world' ... >> >> Maybe someone can give me a hint. >> > Otherwise, what is in /etc/adjtime? >> >> 3019.632059 1112090516 0.000000 >> 1112090516 >> LOCAL > > OK, that means that the clock is supposed to drift for 3020sek per day... > >> > [Hint: man hwclock] So read carefully >> > the "adjust clock" section of that aforementioned man page. >> >> I'll look after that, even if i think that now the clock works again >> [i've adjusted it a few hours ago and didn't loose a minute]. What i >> have done was switching from winter to summer time by manually adding >> one hour to the actual time - maybe my problem has something to do with >> that; For now i'm going to observe my clock closely; Should it continue >> to behave strange i'll look at the suggested manpage. Thanks for your >> help .. > > Yes, it's because you've reset the clock. If you're not using other OS > that don't support this, you should consider to use the UTC for the > hardware clock. The glibc then cares for the daylight savings time and > timezone. > > When you reset the clock, hwclock does interpret this as correcting a > wrong time and calculates the drift from that and write it to /etc/ > adjtime. You should replace the first number in /etc/adjtime to "0.0" > to reset the drift.
Thanks - that solved my problem ! > Otherwise your hardware time will be reset on next > boot with the calculated drift. It's off again, then. That's because > time is read only at boot time and may be written to the hwclock at > shutdown (depends on boot scripts, but i think it's done this way). On > next bootup the hw clock is supposed to be off depending on the drift > and is "corrected" then. > > So it seems to me that your problem is not yet solved... But it's easy > to do as you see. > > > HWH > > PS: You seem to live in a german speaking area like me, so this may be > interesting: http://www.linux-ag.de/linux/LHB/node149.html > it's a little out of date (uses "clock" instead of "hwclock") but the > general concepts are well described. > -- > [email protected] <mailto:> mailing list antonio -- [email protected] mailing list
