February 13th, UNIX Time Will Reach 1234567890
mikesd81 writes "Over at Linux Magazine Online, Jon maddog Hall writes that on Friday the 13th, 2009 at 11:31:30pm UTC UNIX time will reach 1,234,567,890. This will be Friday, February 13th at 1831 and 30 seconds EST. Matias Palomec has a perl script you an use to see what time that will be for you:
perl -e 'print scalar localtime(1234567890),"\n";' Now, while this is not the UNIX epoch, Alan Cox does assure us that Linux is now working on 64-bit time, and the UNIX epoch 'roll-over' would happen about the time that the sun burnt out."
Is that with or without leap seconds?
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
...it's my birthday. I've been telling people for years that my birthday is at 1234567890.
It takes a man to suffer ignorance and smile
Be yourself no matter what they say
The standard unix date command will suffice:
date -d @1234567890
http://coolepochcountdown.com/
The World Wide Web is dying. Soon, we shall have only the Internet.
TIZZLE:~ ben$ perl -e 'print localtime(1234554321) ."\n";'
Fri Feb 13 13:45:21 2009
Apparently a palindrome is one the same day!
Or any OS, for that matter.
And now a bit of topical humor so this post isn't purely an exercise in pointing out the obvious: "Every day is a long day, because 86400 seconds won't fit in a short."
The World Wide Web is dying. Soon, we shall have only the Internet.
Alan Cox does assure us that Linux is now working on 64-bit time, and the UNIX epoch 'roll-over' would happen about the time that the sun burnt out."
This is just the sort of short-sighted thinking that lead to our recent Y2K hysteria, except this time our poor beleaguered descendents will be in the middle of an exodus from the solar system when all their legacy systems throw simultaneous exceptions. This will of course cause their engine and guidance systems to fail, so that the last dying gasps of humanity will consist of:
However, considering that OSX is based on BSD, you can also get Apple pi.
Good, inexpensive web hosting
Raw unix time is simply a count of seconds since a defined point in time - and has nothing to do with leap seconds. Leap seconds only come into play when converting to human readable display format (along with timezones and DST). Leap seconds have been handled for some time by the zoneinfo library used by most unix and linux distros. Even Java handles leap seconds with my port of zoneinfo to a Java TimeZone implementation.
The tzdata package included in most Linux distros includes leapsecond data in the "right" directory. You can find out the time including leapseconds by setting your TZ environment variable to "right/...". For instance:
$ TZ="right/US/Eastern" date; TZ="US/Eastern" date
Sun Feb 8 17:52:42 EST 2009
Sun Feb 8 17:53:06 EST 2009
The french tried it. It failed.
If any post should be marked redundant...
Thus proving TMTOWTDI. ;)
Teenage mutant turtle on wild turtle date...? What the hell does I stand for?!