RE: [SLUG] hwclock, date, and time zones ...
> >If the sequence > # hwclock --hctosys > # date >shows the correct time, then > delay some time > # date >shows an incorrect time, then the issue is that something else >is skewing the system time after the initial sequence has been run. > >My guess is you're running ntpdate or rtime from a cron job or >something, that's getting the time from another machine and >setting the local clock. > Yeah, I used ntpdate to set the time initially but ntpd is not running and I don't see it happening anywhere else (cron, init, etc). Looks like it was /etc/adjtime that was causing the skew (is that possible?). Blowing it away and letting it recreate it has cleared things up as the /etc/adjtime values before: -1714.782194 1055295468 0.00 Were very different than after: 0.00 1055296402 0.00 I s'pose I should man hwclock and actually read rather than skim (cause it explains all this very well, doh!) ... But what would be the fun in that! Thanks for all the help! august -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] hwclock, date, and time zones ...
> "Jamie" == Jamie Wilkinson <[EMAIL PROTECTED]> writes: Jamie> 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. Jamie> Check what /etc/localtime points to, if it is a symlink; if not Jamie> copy over /usr/share/zoneinfo/Australia/Sydney on top of it to Jamie> make sure (though I don't know if Red Hat's Jamie> /etc/sysconfig/clock will do that for you). If the sequence # hwclock --hctosys # date shows the correct time, then delay some time # date shows an incorrect time, then the issue is that something else is skewing the system time after the initial sequence has been run. My guess is you're running ntpdate or rtime from a cron job or something, that's getting the time from another machine and setting the local clock. -- Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au You are lost in a maze of BitKeeper repositories, all slightly different. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
Re: [SLUG] hwclock, date, and time zones ...
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 "/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
Re: [SLUG] hwclock, date, and time zones ...
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 "/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. After setting the system time, and saving UTC to the hardware clock, remove /etc/adjtime or else your machine will have odd ideas about clock drift on your next boot. -- [EMAIL PROTECTED] http://spacepants.org/jaq.gpg -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
[SLUG] hwclock, date, and time zones ...
Hi all, I am having some trouble understanding how to get the software clock to stay set on my red hat 9 box. 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. Then, about 5 minutes later, I type date again and it is suddenly 10 hours ahead! Cleary I've got time zone issues ... /etc/sysconfig/clock shows: ZONE="Australia/Sydney" UTC=false ARC=false But this is the same as on my red hat 8 box, which works happily. What am I missing? Thanks, August Simonelli -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
