| 1 |
On 27 January 2006 18:10, Michael A. Smith wrote: |
| 2 |
> Abhay Kedia wrote: |
| 3 |
> > I manually set correct time using sites like worldtimezone.com. Then, I |
| 4 |
> > shutdown the system and boot after a few hours. What I see is that Gentoo |
| 5 |
> > sets the system time to the same one at which I halted it. For example if |
| 6 |
> > I shutdown 4 hours ago at 14:00 hrs and boot at 18:00 hrs, it will still |
| 7 |
> > set the time to 14:00 hrs instead of the correct time. |
| 8 |
> |
| 9 |
> <snip> |
| 10 |
> |
| 11 |
> > here is my /etc/conf.d/clock. |
| 12 |
> > |
| 13 |
> > --------------------------------- |
| 14 |
> > # /etc/conf.d/clock |
| 15 |
> > CLOCK="local" |
| 16 |
> > CLOCK_OPTS="" |
| 17 |
> > CLOCK_SYSTOHC="no" (have tried both yes and no) |
| 18 |
> > SRM="no" |
| 19 |
> > ARC="no" |
| 20 |
> > --------------------------------- |
| 21 |
> > |
| 22 |
> > I am not using ntp or any other such softwares |
| 23 |
> |
| 24 |
> Hmm, according to the initscript, /etc/init.d/clock isn't supposed to |
| 25 |
> care about the CLOCK_SYSTOHC option until stop(). But it is supposed |
| 26 |
> to set the *system* clock to the hardware clock, so that if the |
| 27 |
> hardware clock is right at boot time, so should be the system clock. |
| 28 |
> |
| 29 |
> I'm not sure, but I suspect that somehow the clock device that |
| 30 |
> /sbin/hwclock is supposed to be talking to is actually static for |
| 31 |
> some reason, and doesn't match your BIOS clock. |
| 32 |
|
| 33 |
The device hwclock connects to *is* the BIOS clock. |
| 34 |
|
| 35 |
Uwe |
| 36 |
|
| 37 |
-- |
| 38 |
Unix is sexy: |
| 39 |
who | grep -i blonde | date |
| 40 |
cd ~; unzip; touch; strip; finger |
| 41 |
mount; gasp; yes; uptime; umount |
| 42 |
sleep |
| 43 |
-- |
| 44 |
gentoo-user@g.o mailing list |
Archives