On 27 January 2006 18:10, Michael A. Smith wrote: > Abhay Kedia wrote: > > I manually set correct time using sites like worldtimezone.com. Then, I > > shutdown the system and boot after a few hours. What I see is that Gentoo > > sets the system time to the same one at which I halted it. For example if > > I shutdown 4 hours ago at 14:00 hrs and boot at 18:00 hrs, it will still > > set the time to 14:00 hrs instead of the correct time. > > <snip> > > > here is my /etc/conf.d/clock. > > > > --------------------------------- > > # /etc/conf.d/clock > > CLOCK="local" > > CLOCK_OPTS="" > > CLOCK_SYSTOHC="no" (have tried both yes and no) > > SRM="no" > > ARC="no" > > --------------------------------- > > > > I am not using ntp or any other such softwares > > Hmm, according to the initscript, /etc/init.d/clock isn't supposed to > care about the CLOCK_SYSTOHC option until stop(). But it is supposed > to set the *system* clock to the hardware clock, so that if the > hardware clock is right at boot time, so should be the system clock. > > I'm not sure, but I suspect that somehow the clock device that > /sbin/hwclock is supposed to be talking to is actually static for > some reason, and doesn't match your BIOS clock.
The device hwclock connects to *is* the BIOS clock. Uwe -- Unix is sexy: who | grep -i blonde | date cd ~; unzip; touch; strip; finger mount; gasp; yes; uptime; umount sleep -- gentoo-user@gentoo.org mailing list
