On Wed, Jun 11, 2003 at 11:21:09AM +1000, Jamie Wilkinson wrote: > This one time, at band camp, August Simonelli wrote: > >Typing hwclock -r reports the correct time, so I know the hardware clock > >is ok. > >I then do hwclock --hctosys to set the system time. > >When I type date it is correct. > > Check what /etc/localtime points to, if it is a symlink; if not copy over > /usr/share/zoneinfo/Australia/Sydney on top of it to make sure (though I > don't know if Red Hat's /etc/sysconfig/clock will do that for you). > > date --set "yyyy/mm/dd hh:mm:ss" will set the system clock to the local > time, then a hwclock --systohc will save it to the hardware clock (which I > suppose is opposite to what you want). Note that the hwclock will > be saved in UTC... > > >Then, about 5 minutes later, I type date again and it is suddenly 10 > >hours ahead! > > ah yes. Because your hardware clock is correct, your system will add 10 > hours to that.
There is an option in most distributions to run the hardware clock at the local time, this allows other OSes which are on your system to "share" the clock. If you are not dual(or quad!)-booting, it is better to have the hardware on UTC, as this does not change for daylight saving, so if your computer is off for the changeover period there is no problem. cheers, Woody -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
