[EMAIL PROTECTED] wrote: > It has recently come to my attention while compiling python that my > computer's clock was reset somehow.The date read 1-1-1903.
Thank you for your report. But in order for someone to diagnose and debug the problem more information will be needed. Enough information to completely recreate the problem will be required. Please read the FAQ for bug reporting guidelines. http://www.gnu.org/software/fileutils/doc/faq/ What was the exact commands you used to see your problem? And what was the exact version of the 'date' command that you used? date --version Date on my computer is showing correct four digit dates. date -R Fri, 14 Mar 2003 10:54:07 -0700 > This was a few days ago.I believe that the time() routines have not > accounted for four digit years Actually, time() does not roll over until 2038 when the 32-bit seconds since 1970 rolls over. By then I hope to be running with a 64-bit time field on a newer computer. > I'm sure i'm not the only one with this bug. Hmm... So far no one else has reported it. Being 2003 now it would be likely. Therefore you might be the only one with the bug. :-) Bob _______________________________________________ Bug-sh-utils mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-sh-utils
