(Yet Another Y2K Problem)

I used to use 'nist' to sync my system's time.  This is NOT the Perl script
of the same name to be found in Freshmeat, it's a compliled executable.  I
don't know where I originally found it, but either *it* or the server it
pulls from by default is not compliant.  It returns the current time, but
it sets the system date to the current day and month, *1910*.

I was experiencing lots of oddness until this was fixed.  Fortunately, the
accompanying call to `hwclock` to force the system date into HW was
failing.  At the time, I assumed this meant either hwclock was goofy or my
system's BIOS was goofy.  This *may* have been the cause of a strange Java
lockup that involved a Java clock that read my system time and may have caused
Gnome's panel to stop coming up.  That's most likely from the system date
being changed so radically in mid-stream, not from odd-date sensitivity.

Fortunately the BIOS is OK and `/sbin/hwclock --hctosys` restored the
proper system date.

I don't know where I got this, I can't find it anymore, but beware.

-W-


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to