No it is the hwclock program that is called from your rc scripts that sets the system clock; here is how it works: When you boot the system; the kernel clock is unset. You run hwclock or hwclock -u if your hardware clock keeps gmt. this sets the kernel's clock to the cmos clock. After this point; typing date will yield the right date. gettimeofday and other clock functions should return correct local time. As the machine shuts down; an rc.. script runs hwclock -u -w or hwclock -w if the time is localtime in the hardware clock. If the kernel is told that the time source is synchronized by ntpd or similar; it will write the time value back to the cmos clock every 11 minutes which is optimal for a room temperature quartz oscillator or so they tell me. You can tinker with this using adjtimex and friends. Regards, Kerry. On Sun, Aug 25, 2002 at 07:52:01AM -0500, Gregory Nowak wrote: > Hi all. > > I was pretty sure that there was a config option when doing make config where you had to answer "y" to something about the hardware clock being set to gmt. However, I've gone through the config twice, and can't find it. My kernel is 2.4.19. > > Was this perhaps in the 2.2.x kernels, or am I simply imagining things? > Thanks to Adam for the info about timeconfig. > Greg > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > -- Kerry Hoath: kerry at gotss.net kerry at gotss.eu.org or kerry at gotss.spice.net.au ICQ: 8226547 msn: kerry at gotss.net Yahoo: kerryhoath at yahoo.com.au
