[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: date-clock problem
- From: Bob McClure Jr <robertmcclure earthlink net>
- To: redhat-install-list redhat com
- Subject: Re: date-clock problem
- Date: Tue, 3 Apr 2001 20:47:32 -0500
When you boot, the system time is set from the hardware clock. When
you use the "date" command to set the system clock, the hardware clock
is unaffected. To sync the hardware clock from the system clock, use:
hwclock --systohc
On Wed, Apr 04, 2001 at 08:23:01AM +0800, Horace G. Friend III wrote:
> Hi,
>
> This seems like a basic question but I just can't seem to hack it.
>
> My motherboard batt. is about to go pfft and everytime I boot my pc (for
> the past week) the system time is always delayed by about 2 hrs.
>
> So I set it right with the date command [date MMDDhhmmCCYY]. Then I
> re-booted to windows ('scuse me) and saw that the time displayed is
> still incorrect (delayed by about 2 hrs).
>
> So re-booted back to linux and checked the output of the date command
> which turned out right as I have earlier set it to be. Then I ran the
> command clock which showed a different time.
>
> I've read from the man pages that the date command reads or sets the
> system date and time while the clock command determines the processor
> time.
>
> What's the difference between the system and processor time. Aren't they
> supposed to be the same? If so how can I get them to be in sync?
>
> Thanks.
>
> --
> Horace G. Friend III
> okee mail com
> GnuPG DSA/ElGamal Key Fingerprint
> 9295 80C4 C723 621B 9C2D B53E D432 7936 4CA9 8AD6
Cheers,
--
Bob McClure, Jr. | Dyslexia means
Bobcat Open Systems, Inc. | never having to say
robertmcclure earthlink net | you're ysror.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]