
	Where results make sense

Topic: Year 2038 problem

	Year 2038 problem - Wikipedia, the free encyclopedia
		In computing, the year 2038 problem may cause some computer software to fail in or about the year 2038.
		The problem affects programs that use the POSIX time representation, which represents time as the number of seconds (ignoring leap seconds) since January 1, 1970.
		The year 292,277,026,596 problem is not, however, widely regarded as a pressing issue.
	en.wikipedia.org /wiki/Year_2038_problem (344 words)

	Talk:Year 2038 problem - Wikipedia, the free encyclopedia
		Batkins wrote that the 2038 problem has nothing to do with C/C++, which is certainly not true: the influence of C is the only reason the problem affects non-Unix platforms at all.
		The problem is Unix/Posix specific in the sense that other platforms have their own time-related calls, and software which uses those calls exclusively will not be subject to the year 2038 problem at all.
		The problem could have been solved from the beginning if integer types had a fixed size in C. It was thought C should run on various hardware platforms and limiting the sizes of the fundamental types may have limited the use of C. For an example characters are not guaranteed to be 8-bit.
	en.wikipedia.org /wiki/Talk:Year_2038_problem (2779 words)

	Encyclopedia: Year 2038 problem (Site not responding. Last check: 2007-11-02)
		The year 2000 problem (also known as the Y2K problem and the millennium bug) was a common practice (not a flaw) in computer program design that caused some date-related processing to operate incorrectly for dates and times on and after January 1, 2000.
		The year 2000 problem (also known as the Y2K problem and the millennium bug) was a flaw in computer program design that caused some date-related processing to operate incorrectly for dates and times on and after January 1, 2000.
		Another related problem for the year 2000 was that it was a leap year even though years ending in "00" are normally not leap years.
	www.nationmaster.com /encyclopedia/Year-2038-problem (1258 words)

	The Year 2038 Problem
		Year 2038 bugs, on the other hand, occur when a program reads in a date and carries it around from one part of itself to another.
		A program storing these dates as days, months, and years would first have to compare the years, then compare the months if the years were the same, then compare the days if the months were the same, for a total of 3 comparison operations.
		So, even if you were to fix every Year 2000 Bug in a program in such a way that users and databases could use years as large as 9999, it wouldn't even brush on any of the Year 2038 Bugs lurking within the same program.
	pw1.netcom.com /~rogermw/Y2038.html (1727 words)

	Year 2000 problem
		It was thought computer programs could stop working or produce erroneous results because they stored years with only two digits and that the year 2000 would be represented by '00' and would be interpreted by software as the year 1900.
		In the years prior to 2000, some corporations and governments, when they did testing to determine the extent of the potential impact, reported that some of their critical systems really would need significant repairs or risk serious breakdowns.
		The problem was first recognised in 1958 by Bob Bemer as a result of work on genealogical software.
	www.brainyencyclopedia.com /encyclopedia/y/ye/year_2000_problem.html (2239 words)

	RFC 2626 (rfc2626) - The Internet and the Millennium Problem (Year 2000)
		For example, the first leap year, the first "double digit" day (January 10, 2000), January 1, 2001, etc. There is not one place where days have been used in the protocols defined by the RFC series so there is little reason to believe that any of these special dates will have any impact.
		Given a two-digit year YY, if YY is greater than or equal to 50, the year shall be interpreted as 19YY; and where YY is less than 50, the year shall be intrepreted as 20YY.
		This problem is avoided entirely by taking the RFC 1123 change as a requirement, rather than merely as a recommendation.
	www.faqs.org /rfcs/rfc2626.html (8306 words)

	The Year 2038 Problem
		In case you think we can sit on this issue for another 30 years before addressing it, consider that reports of temporal echoes of the 2038 problem are already starting to appear in future date calculations for mortgages and vital statistics!
		In the first month of the year 2038 C.E. many computers will encounter a date-related bug in their operating systems and/or in the applications they run.
		By the year 2038, the time_t representation for the current time will be over 2 140 000 000.
	www.pro-networks.org /forum/about51658.html (1446 words)

	Howstuffworks "What is the Year 2038 problem?"
		The Year 2000 problem is understood by most people these days because of the large amount of media attention it received.
		Most programs written in the C programming language are relatively immune to the Y2K problem, but suffer instead from the Year 2038 problem.
		This problem arises because most C programs use a library of routines called the standard time library.
	www.howstuffworks.com /question75.htm (448 words)

	In nature (Site not responding. Last check: 2007-11-02)
		This problem is somewhat easier to fix than the Y2K problem on mainframes, fortunately.
		This is possible because the library encapsulates the whole time activity with its own time types and functions (unlike most mainframe programs, which did not standardize their date formats or calculations).
		So the Year 2038 problem should not be nearly as hard to fix as the Y2K problem was.
	www.geocities.com /ssquare6/answer1.html (362 words)

	Y2K38 - Year 2038 Problem (Site not responding. Last check: 2007-11-02)
		The Y2K38 problem has been described as a non-problem, given that we are expected to be running 64-bit operating systems well before 2038.
		While 32-bit CPUs may be obsolete in desktop computers and servers by 2038, they may still exist in microcontrollers and embedded circuits.
		Such embedded functions present a serious maintenance problem for Y2K38 and similar rollover issues, since the package part number and other markings typically give no indication of the internal function.
	vancouver-webpages.com /time/Y2K38.html (365 words)

	Year 2000 Compliance (Site not responding. Last check: 2007-11-02)
		Therefore, ClibPDF functions are expected to operate correctly until year 2037 or as long as dates beyond year 2037 are not used during processing.
		If dates beyond year 2037 are used, the 32-bit integer (maximum positive integer is (2^31)-1) will roll over to a negative number (see below), and incorrect results and/or a program crash may occur.
		Any continued use of binary executables created on current systems will result in program mulfunctions after year 2037 or whenever dates beyond 2037 are used during processing.
	www.fastio.com /year2000.html (372 words)

	Editor's Note
		As in many aspects of modern life, the anxiety at the end of the 20th century appears to be technology-driven, manifesting itself as the "Year 2000 Problem," aka Y2K or millennium problem.
		The problem is similar to that found in the UNIX operating system.
		Note that the described problems can be delayed by about 292 billion years, if the protocols are upgraded to 64-bit timestamps (Similarly, UNIX systems can postpone the problem by moving to a 64-bit architecture).
	www.comsoc.org /~ni/public/1999/jan/niednot.html (1048 words)

	HP OpenVMS systems - Year 2000
		February 28, 2000 to February 29, 2000 (to verify leap year calculation; Tuesday, February 29, 2000 is a valid date in the Gregorian calendar)
		The Year 2038 problem is analogous to the Year 2000 problem, but results from overflows in the storage of time and date values in C programs.
		The Year 2038 problem is expected to have minimal adverse effects for the OpenVMS operating system because the C date format is not the native date storage format used on OpenVMS.
	h71000.www7.hp.com /openvms/products/year-2000/testing.html (691 words)

	The Connection, v.19 n.3 (Site not responding. Last check: 2007-11-02)
		Actually, it was a Year 2038 bug, and it knocked out my e-mail capability for over two weeks.
		John explained that if the system date were set to later than Year 2038, the MAPI Spooler would crash.
		I'm sure that these problems are being addressed in today's operating systems and compilers.
	www.itug.org /member/services/connection/v19n3a9.cfm (569 words)

	Project 2038 FAQ
		"Three years ago, I had several servers timed to a single (note I say single) NTP located at a university that, unbeknownst to me, was checking for the Unix equivalent of the Y2K bug that will occur in the year 2038.
		The 2038 problem may well cause more serious problems because it involves the basic system timekeeping functions from which most other time and date information is derived.
		The sun is estimated at present to be about four and a half billion years old, and it may last another five billion years before running out of hydrogen and turning into a white dwarf star.
	maul.deepsky.com /~merovech/2038.html (2297 words)

	Inside (Site not responding. Last check: 2007-11-02)
		This explains why there was no real year 2000 problem on Unix/Linux based systems.
		Since the date is handled in this manner, the turn of the millennium or the year 2000 was just another second on the counter and different to any other one.
		Unfortunately, there is drawback to this method, the so called ‘Year 2038’ problem.
	www.pec.edu /cybyrus/10thissue/unix.htm (205 words)

	[No title]
		Nesser Informational [Page 17] RFC 2626 The Internet and the Millennium Problem (Year 2000) June 1999 15.2 Specifics One is a common practice of writing serial numbers in zone files as if they represent a date, and using only two digits of the year.
		Nesser Informational [Page 19] RFC 2626 The Internet and the Millennium Problem (Year 2000) June 1999 16.2.4 Dates in Mobile Network Tracing Records (RFC 2041) The RFC specifies trace headers and footers with date fields that are character arrays of size 32.
		Nesser Informational [Page 23] RFC 2626 The Internet and the Millennium Problem (Year 2000) June 1999 RFC 1479 which specifies IDPR Version 1, defines a timestamp field in section 1.5.1, which is a 32 bit unsigned integer number of seconds since January 1, 1970.
	www.ietf.org /rfc/rfc2626.txt (8593 words)

	The Year 2038 Problem
		A time_t value of this exact number, 2 147 483 647, represents January 19, 2038, at 7 seconds past 3:14 AM Greenwich Mean Time.
		In a 64-bit program, a time_t could represent any date and time in the future out to 292 000 000 000 A.D., which is about 20 times the currently estimated age of the universe.
		Scheduling software, billing programs, personal reminder calendars, and other such pieces of code that set dates in the near future will fail as soon as one of their target dates exceeds 19-Jan-2038, assuming a time_t is used to store them.
	lakmal.blogster.com /year_2038_problem.html (1084 words)

	The year 2038 bug
		The year-2038 bug is similar to the Y2K bug in that it involves a time wrap not handled by programmers.
		In the case of Y2K, many older machines did not store the century digits of dates, hence the year 2000 and the year 1900 would appear the same.
		There are however several other problems with date handling on machines in the world today.
	www.2038bug.com (416 words)

	Chakra’s Graffiti » Blog Archive » Year 2038 problem
		Have you heard about the Year 2038 problem, which the doomsayers say would cause aircrafts to nosedive, satellites to fall out of orbit and what not?
		Though ‘How Stuff Works‘ says that the problem is not as difficult as it was with Y2K, I could see IT majors licking their lips in anticipation of 2038 bug fix projects.
		This entry was posted on Thursday, June 16th, 2005 at 11:49 am and is filed under Technical.
	www.chakkarapani.com /graffiti?p=55 (981 words)

	The Republic of Geektronica » Blog Archive » Spam Karma and Unix Epoch Date Zen
		The problem affects programs that use the POSIX time representation, which represents time as the number of seconds since January 1, 1970.
		This representation is standard in Unix-like operating systems and 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.
		This entry was posted on Friday, October 28th, 2005 at 4:07 pm and is filed under Culture of Geekdom.
	www.geektronica.com /2005-10-28-spam-karma-and-unix-epoch-date-zen (424 words)

	The Year 2038 Problem \| Sig9
		Just when you thought that world was saved from a mammoth of a problem called Y2k[check out Y2k for an associated set of problems], up comes another one.
		For the uninitiated, time_t is a data type used by C and C++ programs to represent dates and times internally.
		Since one year lasts for a little over 31 000 000 seconds, the time_t representation of January 1, 1971 is about 31 000 000, the time_t representation for January 1, 1972 is about 62 000 000, et cetera.
	sig9.com /node/194 (276 words)

	The Ultimate Fusion of Life: Me N U
		By the year 2038, the time_t representation for the current time will be
		problem should not be nearly as hard to fix as the Y2K problem was.
		Years afterward, the nobleman's son was stricken with pneumonia.
	www.freewebs.com /djchantz4u/factsnsurprises.htm (1708 words)

	David Fries - Year 2038 Date Problem
		Corporations begin three year campaign to upgrade all computer software; Supreme Court hears scare tactics on 2038 bug driving said upgrades.
		The argument +%s tells date to print out the number of seconds since the standard Unix start time which is January 1970 00:00:00 UTC and is the computer epoch start of time.
		On January 18th 2038 computers using this system will no longer be able to represent the date correctly since it can no longer count that high.
	david.fries.net /thoughts/year2038.php (758 words)

	The Year 2038 problem revisited... \| Sig9
		The Year 2038 problem has been noted and been changed since MFC 6.0 release for Windows programmers.
		With the Year 2000 crisis looming ahead, many developers choose COleDateTime because of its much larger range.
		Any application that uses CTime will need to be reworked in approximately 40 years, since the maximum value is the year 2038.
	sig9.com /node/265 (241 words)

	comp.unix.misc: By Thread
		Re: [OT] Re: The Year 2038 Problem Leor Zolman
		Re: [OT] Re: The Year 2038 Problem Martin Dickopp
		Re: [OT] The Year 2038 Problem Stephen Sprunk
	unix.derkeiler.com /Newsgroups/comp.unix.misc/2004-06 (624 words)

	New Technology for Year 2000 Problem Tools
		If the intended value is 2000 --- such as when 00 represents the value of the current year in a computation performed after the calendar rolls over on January 1, 2000 --- then a faulty computation may be carried out.
		With some further analysis of the spectra, for each such path that shows up in the spectral difference, it is possible to identify the shortest prefix that distinguishes it from all of the paths in the other path set (see below).
		Furthermore, the path-spectrum comparison technique is actually applicable to a much wider range of software-maintenance problems than just the Y2K problem; it offers new perspectives on program testing, on the task of creating test data, and on what tools can be created to support program testing.
	www.cs.wisc.edu /~reps/y2k_technology.html (899 words)

Try your search on: Qwika (all wikis)