Slashdot Mirror


Billennium's Over - Anything Break?

An Anonymous Coward writes: "The billennium party at OpenProjects.Net rocked! Check out the log for the whole event over here. Please don't forget to use one of the mirrors. Thanks :-)" Well, anyone have anything break due to the rollover?

5 of 265 comments (clear)

  1. Anything Break? by rchatterjee · · Score: 4, Insightful

    From my understanding the major problem doesn't occur till 2038 when 32-bit time reaches 2,147,483,647 seconds. 2,147,483,647 is the biggest number a 32-bit system can register.

  2. Re:really small stuff by Anonymous Coward · · Score: 1, Insightful


    Ah, this proves the point that people must have written extraordinarily bad code to get caught to this bug (I'm not directing at you, I've done worse). Thats the advantage of these "rollover" bugs. All the hastily coded apps come out of the woodwork.

    If you insist on using the filename to find the recent file, you should have set it up to find that 1,000,000,000 is actually a bigger integer than 999,999,999 .. rather than relying on a rather funky sort.

    Why dont you check the file timestamp instead of the file name? I assume you have a valid reason such as the file getting transported around?

  3. Re:My mail client - pronto broke. by Chagrin · · Score: 5, Insightful

    The fact that Perl has vague distinctions between strings and numbers has very little to do with the situation at hand. The problem with the billennium bug is that there's a risk that programmers did not allocate enough digits to hold a date correctly; since both Perl and Python reallocate memory to handle larger values internally, your Python will succeed or fail in an equal number of situations as Perl. It's not an issue of the actual program language, the issue is how the date is persistently stored when the program ends (a database, columnar text file, or whatever).

    You're not flamebait because you're a Python bigot, you're flamebait because your post is an invalid rant and off-topic.

    --

    I/O Error G-17: Aborting Installation

  4. Re:really small stuff by zdzichu · · Score: 2, Insightful

    >The simple solution is to move the old 999 files >to another directory. This problem wouldn't have >cropped up since 1973 when it passed eight 9s,
    >and won't happen again for another 300 years when
    >it passes ten 9s.

    Do I remember correctly that another 300 years won't happen, because in 2038 timer will roll-over?
    If we not got 64-bit timestamp, of course.

    --
    :wq
  5. No problems here... by edashofy · · Score: 3, Insightful

    ...I run Windows :)