2030s - 2038, 2030, 2037, 2039, 2034, 2035, 2036, 2033, 2032, 2031, Year 2038 Problem (Paperback)


Chapters: 2038, 2030, 2037, 2039, 2034, 2035, 2036, 2033, 2032, 2031, Year 2038 Problem. Source: Wikipedia. Pages: 20. Not illustrated. Free updates online. Purchase includes a free trial membership in the publisher's book club where you can select from more than a million books without charge. Excerpt: The year 2038 problem (also known as Unix Millennium Bug, Y2K38 by analogy to the Y2K problem) may cause some computer software to fail before or in the year 2038. The problem affects all software and systems that store system time as a signed 32-bit integer, and interpret this number as the number of seconds since 00:00:00 UTC on Thursday, 1 January 1970. The furthest time that can be represented this way is 03:14:07 UTC on Tuesday, 19 January 2038. Times beyond this moment will "wrap around" and be stored internally as a negative number, which these systems will interpret as a date in 1901 rather than 2038. This will likely cause problems for users of these systems due to erroneous calculations. Further, while most programs will only be affected in or very close to 2038, programs that work with future dates will begin to run into problems much sooner. For example, a program that works with dates 20 years in the future will have to be fixed no later than in 2018. Because most 32-bit Unix-like systems store and manipulate time in this format, it is usually called Unix time, and so the year 2038 problem is often referred to as the Unix Millennium Bug. However, any other non-Unix operating systems and software that store and manipulate time this way will be just as vulnerable. In May 2006, reports surfaced of an early manifestation of the Y2038 problem in the AOLserver software. The software was designed with a kludge to handle a database request that should "never" time out. Rather than specifically handling this special case, the initial design simply specified an arbitrary time-out date in the future. The default configurati...More: http: //booksllc.net/?id=30012

R343

Or split into 4x interest-free payments of 25% on orders over R50
Learn more

Discovery Miles3430
Delivery AdviceOut of stock

Toggle WishListAdd to wish list
Review this Item

Product Description

Chapters: 2038, 2030, 2037, 2039, 2034, 2035, 2036, 2033, 2032, 2031, Year 2038 Problem. Source: Wikipedia. Pages: 20. Not illustrated. Free updates online. Purchase includes a free trial membership in the publisher's book club where you can select from more than a million books without charge. Excerpt: The year 2038 problem (also known as Unix Millennium Bug, Y2K38 by analogy to the Y2K problem) may cause some computer software to fail before or in the year 2038. The problem affects all software and systems that store system time as a signed 32-bit integer, and interpret this number as the number of seconds since 00:00:00 UTC on Thursday, 1 January 1970. The furthest time that can be represented this way is 03:14:07 UTC on Tuesday, 19 January 2038. Times beyond this moment will "wrap around" and be stored internally as a negative number, which these systems will interpret as a date in 1901 rather than 2038. This will likely cause problems for users of these systems due to erroneous calculations. Further, while most programs will only be affected in or very close to 2038, programs that work with future dates will begin to run into problems much sooner. For example, a program that works with dates 20 years in the future will have to be fixed no later than in 2018. Because most 32-bit Unix-like systems store and manipulate time in this format, it is usually called Unix time, and so the year 2038 problem is often referred to as the Unix Millennium Bug. However, any other non-Unix operating systems and software that store and manipulate time this way will be just as vulnerable. In May 2006, reports surfaced of an early manifestation of the Y2038 problem in the AOLserver software. The software was designed with a kludge to handle a database request that should "never" time out. Rather than specifically handling this special case, the initial design simply specified an arbitrary time-out date in the future. The default configurati...More: http: //booksllc.net/?id=30012

Customer Reviews

No reviews or ratings yet - be the first to create one!

Product Details

General

Imprint

Books + Company

Country of origin

United States

Release date

September 2010

Availability

Supplier out of stock. If you add this item to your wish list we will let you know when it becomes available.

First published

September 2010

Editors

Creators

Dimensions

152 x 229 x 1mm (L x W x T)

Format

Paperback - Trade

Pages

22

ISBN-13

978-1-157-35931-9

Barcode

9781157359319

Categories

LSN

1-157-35931-0



Trending On Loot