The Year 2038 problem(Unix Millennium bug)

try it now...

1. login to yahoo messenger.
2. send instant message to anyone - fine its working...
3. now, change your system date to 19-Jan-2038, 03:14:07 AM or above.
4. Confirm weather your date is changed.
5. again send instant message to anyone...
Your Yahoo Messenger crashes....

* * * YES ALL NETWORK BASED APPLICATION WILL NOT WORK NOW * * *

The year 2038 problem (also known as "Unix Millennium bug", "Y2K38," "Y2K+38," or "Y2.038K" by analogy to the Y2K problem) may cause some computer software to fail before or in the year 2038. The problem affects Unix-like operating systems, which represent system time as the number of seconds (ignoring leap seconds) since 00:00:00 January 1, 1970[1]. This representation also affects software written for most other operating systems because of the broad deployment of C. On most 32-bit systems, the time_t data type used to store this second count is a signed 32-bit integer. The latest time that can be represented in this format, following the POSIX standard, is 03:14:07 UTC on Tuesday, January 19, 2038. Times beyond this moment will "wrap around" and be represented internally as a negative number, and cause programs to fail, since they will see these times not as being in 2038 but rather in 1901. Erroneous calculations and decisions may therefore result.

see this image on wikipedia that will explain 2038 problem more.

Enjoyed reading this article,Now you may want to Subscribe to my RSS feed!or scroll down to leave a comment, or get back to the homepage.

Related Posts by Categories



0 comments:

RSS Entries

Recent Post