At 09:18 PM 5/1/00 -0500, Uncle Meat wrote:
>
>On 02-May-00 John Aldrich opined:
>> I just ran "rdate" and noticed that the clock on my KDE
>> console was about an hour behind. I guess the question is:
>> "Why is it losing time"? The KDE clock on the KPanel is
>> *supposed* to show proper system time, correct?
>>
>> Here's my system stats:
>> Dual-PPro 200, 192 megs of RAM, 18 Gigs of drive space
>> (give or take a few megs) system is running 1 instance of
>> Seti@home and one RC5DES (I had to force a single-instance
>> of RC5DES.) Video is a Voodoo3-3000. Motherboard is a
>> Micronics W6LI-SH04.
>>
>> Any ideas?
>
>How about "spring forward, fall back" as a possibility.
>
>My system changed the clock for daylight stupid time as it should. After a
>reboot it was an hour off (slow). After a time update, it was 2 hours slow
>(no idea on this). I reset it manually, rebooted and it was right.
>
>Beats me why. But, that's my experience. Perhaps you're seeing something
>similar.
>
If it is a Linux only machine, set the clock to utc and forget about the
time change - Linux will handle it for local times for most time zones.
(Don't forget to change /etc/sysconfig/clock...)
As for your clock being off, PC clocks are not known for accuracy. Also,
if you have set the hardware clock from Linux, there is now an adjustment
factor that is applied when ever you reboot. (/etc/adjtime) It can have
some interesting affects if you use hwclock to change for daylight savings
time... On the other hand, it you set the hardware and software clocks
weekly for an accurate source, it can do a very good job of keeping your
clock on time.
Mikkel
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
