>
>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
> "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.
Ja
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.
>
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
/us
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
