Search results
Results from the WOW.Com Content Network
The Network Time Protocol has an overflow issue related to the Year 2038 problem, which manifests itself at 06:28:16 UTC on 7 February 2036, rather than 2038. The 64-bit timestamps used by NTP consist of a 32-bit part for seconds and a 32-bit part for fractional second, giving NTP a time scale that rolls over every 2 32 seconds (136 years) and ...
Time formatting and storage bugs lists other similar problems, often caused by rollover similar to the cause of this year 2038 problem. A GPS week number rollover will coincidentally happen later in 2038, for a different reason than this year 2038 problem.
The leap year problem (also known as the leap year bug or the leap day bug) is a problem for both digital (computer-related) and non-digital documentation and data storage situations which results from errors in the calculation of which years are leap years, or from manipulating dates without regard to the difference between leap years and common years.
A similar problem will occur in 2038 (the year 2038 problem), as many Unix-like systems calculate the time in seconds since 1 January 1970, and store this number as a 32-bit signed integer, for which the maximum possible value is 2 31 − 1 (2,147,483,647) seconds. [50] 2,147,483,647 seconds equals 68 years, and 2038 is 68 years forward from 1970.
Year 2038 problem: a time formatting bug in computer systems with representing times after 03:14:07 UTC on 19 January 2038; GPS week number rollover: time keeping integer rollover caused by the design of the Global Positioning System, which occurs every 19.6 years; 512k day: an event in 2014, involving a software limitation in network routers
Main page; Contents; Current events; Random article; About Wikipedia; Contact us; Help; Learn to edit; Community portal; Recent changes; Upload file
Software timekeeping systems vary widely in the resolution of time measurement; some systems may use time units as large as a day, while others may use nanoseconds.For example, for an epoch date of midnight UTC (00:00) on 1 January 1900, and a time unit of a second, the time of the midnight (24:00) between 1 January 1900 and 2 January 1900 is represented by the number 86400, the number of ...
This means using difftime to compare time_t values and get a difference in seconds (simple subtraction may not work, because the units are arbitrary), mktime to construct a time_t from a struct of real-world values (which uses int for the year, with a base of 1970, so even a 16-bit system would have a 64K-year range,) gmtime and localtime to ...