1000000000000000000000000000000 seconds

In sixteen minutes -- at Sat Jan 10 05:37:04 2004 PST, or Sat Jan 10 13:37:04 2004 GMT -- time_t will be a 31 bit quantity. That is, the number of seconds since the Unix Epoch (Thu Jan 1 00:00:00 1970 GMT) will be 2^30.

    1073741824 decimal
    40000000 hex
    10000000000 octal
    1000000000000000000000000000000 binary

And just think, you were there.

    perl -e 'print localtime(2**30) . "\n"'
    perl -e 'printf "%b\n", time'
Tags: , , ,

22 Responses:

  1. vincel says:

    Was it as good for you as it was for me?

    • vincel says:

      Hah! LJ's timestamp certainly fucked that post up.

    • fo0bar says:

      stop stealing from my picture set!

      (well, it's not "my" picture set, but, ummm... i was here first!)

      • vincel says:

        Congratulations! You beat me to it by a day:

         bleach 20% ls -l 728127
        -rw-r--r-- 1 vincel wheel 2912 Jun 28 2003 728127
        bleach 21% ls -l 353803
        -rw-r--r-- 1 vincel wheel 1682 Jun 27 2003 353803

        But at least I had the grace to attribute the source:

         bleach 22% identify -verbose 728127
        Image: 728127

        Copyright (c) 2003 by Peter Stemmler -- QuickHoney


  2. alynch says:

    I just attempted to explain this to my fianceè... She suddenly got serious and asked, "Is this like Y2K?"

    That just made my morning.

    • magicpacket says:

      No, that doesn't happen until 2038...

      eric@haleakala [10:25am] ~ 3 $ perl -le 'print scalar localtime(2**31-1)'
      Mon Jan 18 19:14:07 2038
      eric@haleakala [10:25am] ~ 4 $ perl -le 'print scalar localtime(2**31)'
      Fri Dec 13 12:45:52 1901
  3. avva says:

    Ooh, thanks for the reminder. I would've missed it otherwise.

  4. malokai says:

    did the world end?

  5. cyn_goth_prog says:

    "My son returns from a fancy East coast college and I'm horrified to find he's a nerd"


  6. ofsilence says:

    And I turn 31! tomorrow...

    • solarbird says:

      31! ?! Gotd dammit, you're old.

      So, um, since you'd have been there - what colour were the dinosaurs?

  7. xxv says:

    But I had posted a countdown(well, up) clock I wrote in Javascript:


  8. transgress says:

    hehe. i posted in my journal on this when slashdot ran a story. AFAIK it's really only a problem for applications that make use of 30b timestamps, which the best that I vould discern lisp would be the major thing affected there? I actually did the man on when the 'world will end'. It's fun to think we will encounter this same problem every so often, im not going to do the math, but when will a 64b timestamp be forced to rollover? I wonder if we will have a y2k repeat around then or not. (yes i realize the y2k problem wasnt a MAX_INT rollover)

  9. unavoidablefate says:

    I'm just thoroughly amused that the GMT time is 1337.

  10. publius_ovidius says:

    As a side note, the "l" (el) switch in Perl will cause a newline to be added after each print. It makes one-liners easier (though the localtime will have to be forced into scalar context).

    perl -le 'print scalar localtime(2**30)'

    perl -le 'printf "%b", time'

  11. violentbloom says:

    and lets not forget it was also my friggin birthday.
    sigh though two hours off