Jump to content


Photo
- - - - -

32-bit systems year 2038 issue.


No replies to this topic

#1 Rob Fantini

Rob Fantini

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 291 posts
  • Gender:Male
  • Location:Haverhill, United States

Posted 11 December 2018 - 09:56 AM

 

I was checking if our pro4 system would work in the year 2100 - started by changing the operating system date [ using a backup virtual system ].

 

2100 did not work, so changed  the date a  until i found the second things would break:

#
# on debian  the 'date' command sets system date
# 
#  for red hat systems,  i am not sure which command is used
#

date  011822142038   
Mon Jan 18 22:14:00 EST 2038

# 1 second later:
date  011822152038
date: invalid date `011822152038'

#
# display the date
#

date
Fri Dec 13 15:54:20 EST 1901

so after posting to the debian forum,  i got this one line answer:

 

 https://en.wikipedia...ar_2038_problem

 

anyone with a pro4 system running on a 32-bit linux [ and perhaps windows ] system has an important issue to deal with.

 

 

NASA has lost at least one satellite - probably due to a related issue.

https://en.wikipedia..._end_of_mission

 

There are projects working on a fix for the issue. this looks promising https://github.com/e...pire/y2038/wiki

 

we use pro4 v4.6 on a debian 4 system , and had intended to stay with 4.6  it works perfect and our systems need few changes .

 

Due to this issue we will purchase a V9 pro4  and prepare to migrate if needed.

 

I will also try get our good old debian etch system patched .

 

 

 

 





Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users