>>>>> "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
